test-design

Generates acceptance criteria, test plans, and test cases from backlog and screen specifications.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/Samind-Samind/projexa --skill test-design-samind-samind
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-design
Source: https://github.com/Samind-Samind/projexa/tree/main/.claude/skills/test-design
Command: npx skills add https://github.com/Samind-Samind/projexa --skill test-design-samind-samind

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing consistent, traceable test documentation (Acceptance Criteria, Test Plans, Test Cases) by hand is slow and error-prone, especially when it must stay aligned with backlog items, feature lists, and per-screen specs. This Skill synthesizes those source documents into structured test artifacts for the Projexa project while enforcing human-in-the-loop confirmation before any file is written. ## Core Features & Use Cases - Acceptance Criteria Generation: Creates Given-When-Then sections per backlog item (SCR) in a single acceptance-criteria.md file, extending it incrementally per scope. - Test Plan Authoring: Produces or updates a project-wide test-plan.md covering scope, test types, environment, risks, and entry/exit criteria. - Per-Feature Test Cases: Writes step-by-step test case files (test-cases/{feature-slug}.md) that reference real AC IDs for traceability. - Use Case: A QA lead asks to create test cases for SCR-006; the Skill verifies the spec and AC exist, asks whether to generate missing AC first, confirms the plan, then delegates file writing to a test-designer sub agent. ## Quick Start Ask the assistant to create acceptance criteria and test cases for a specific screen, for example: create test cases and acceptance criteria for SCR-006.

Frequently Asked Questions about test-design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate test cases from acceptance criteria?▼

Specify the target screen or backlog item (e.g., SCR-006) and request test cases. The Skill checks that acceptance criteria exist for that item first, then writes step-by-step test cases in test-cases/{feature-slug}.md that reference real AC IDs.

How do I write acceptance criteria in Given-When-Then format?▼

Request acceptance criteria for a scope of screens or backlog items. The Skill synthesizes the backlog, feature list, and per-screen specs into Given-When-Then sections appended to a single acceptance-criteria.md file, one section per SCR.

What documents are required before creating test cases?▼

The Skill requires backlog.md, feature-list.md, the per-screen spec files, user-journey.md, and an existing acceptance criteria section for each target screen. If any are missing, it suggests running the prerequisite skills first or narrowing the scope.

Can I update an existing test plan instead of rewriting it?▼

Yes. When test-plan.md already exists, the Skill asks whether to update only changed sections or rewrite the whole file, recommending partial updates by default so previously reviewed content is preserved.

Does the Skill write test documentation files automatically?▼

No file is created or modified without explicit user confirmation. The main loop collects document type, scope, and write mode interactively, then delegates the actual writing to a one-shot test-designer sub agent only after approval.