qa-plan

You generate a structured QA plan by invoking the /qa-plan command, which reads your CDDs and story files to classify stories by test type and outline required automated tests, manual verification, smoke scope, and sign-offs.

Classifying stories by test type involves reading project artifacts like CDDs to assign appropriate validation categories such as API, UI, integration, or data migration, producing a complete QA plan document with test approaches and acceptance criteria traceability.

Acceptance criteria traceability works by mapping each story file to specific test approaches and evidence requirements, ensuring the generated QA plan covers all validation needs and outlines required automated tests and manual verification.

Yes, you can use this QA plan generation for product, API, CLI, or game domains, classifying stories by test type and generating a comprehensive test plan tailored to each specific domain's validation requirements.

The generated sprint QA plan document gets written to production/qa/qa-plan-[scope]-[date].md, providing test approaches, required artifacts, scope, hand-off guidance, and smoke tests before sprint execution.

Yes, you need CDDs and story files as input artifacts to determine scope and tests, allowing the system to classify each story by test type and outline required automated tests, manual verification, and sign-offs.