/qa-impact
Phase: 2 - Planning
Command: /qa-impact
Run: Subsequent cycles (use /qa-requirement for the first cycle)
Allowed tools: Read, Write
What it does
Records what changed between the previous cycle and the current one. Updates the requirements/ folder and qa-plan.md with only the delta - history from previous cycles is preserved below the new dated section.
Most importantly, /qa-impact flags only the domains that need re-running based on what changed. Unchanged domains are explicitly marked as "no re-run needed", so you don't waste time re-testing things that haven't changed.
Inputs
- New requirements (Jira, paste, or questionnaire - same options as
/qa-requirement) - Existing
requirements/files (to compare against) - Existing
qa-plan.md(to update in place)
What it updates
| File | Change |
|---|---|
requirements/requirements-*.md | Prepends new dated section with changed requirements only |
qa-plan.md | Prepends new dated section with updated strategy and re-run flags |
Re-run flags
The updated plan will include a section like:
markdown
### Domain re-run analysis
| Domain | Re-run needed? | Reason |
|--------|---------------|--------|
| API | ✅ Yes | New /payments endpoint added |
| UI | ✅ Yes | Login page redesigned |
| Accessibility | ✅ Yes | Login page redesigned - re-audit required |
| Performance | ❌ No | No load-affecting changes |When to use
| Cycle | Skill to use |
|---|---|
| First cycle on this project | /qa-requirement |
| Second and all subsequent cycles | /qa-impact |
After impact analysis
Run /qa-plan to update the test strategy for the changed domains.