wa:design-qa

A QA plan maps feature acceptance criteria IDs to deterministic test layers like unit, integration, E2E, security, and performance. It defines coverage targets, component ownership, execution order, and environment requirements for implementation teams.

Structure test coverage by selecting lite, standard, or strict rigor modes. Each mode adjusts the breadth of unit, integration, E2E, security, and performance testing applied to your acceptance criteria across local and CI/staging environments.

You need a feature description alongside available FRD, architecture, design, and NFR artifacts. These documents provide the acceptance-criteria IDs used to determine test layer mapping, component ownership, priority, and automation expectations.

Generate a QA plan by executing in plan-mode with your feature description. It produces a verified markdown artifact at docs/{feature}/QA-PLAN.md containing scope, coverage targets, environment requirements, execution order, and next-step recommendations.

Yes, you can plan security testing and performance coverage. The tool maps acceptance criteria to security and performance test layers under standard or strict rigor modes, defining specific coverage targets for local and CI/staging environments.