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.