qa-planning

Run qa-planning on the story to identify risks across six categories (technical, security, performance, data, business, operational), score each with probability times impact, and receive a risk matrix with mitigation strategies saved alongside the story file.

Use unit tests for pure logic without external dependencies, integration tests for component interactions and database operations, and e2e tests only for critical user journeys. The Skill applies these decision criteria to each acceptance criterion automatically.

Any risk scoring 9 (critical) maps to a gate FAIL unless waived, any score of 6 or higher maps to CONCERNS, and lower scores map to PASS. The Skill emits a risk_summary YAML block for direct inclusion in the gate file.

Yes, the same risk profiling and test design workflows apply to tasks. Outputs use the task naming convention task.{id}.risk.{num} and task.{id}.test-design.{num} instead of the story-based file names.

Skip it for trivial changes with no acceptance criteria or risk surface, such as typo fixes or config tweaks. The Skill is designed for stories and features where failure would have measurable business, security, or data impact.