/qa-requirement

Phase: 2 - Planning
Command: /qa-requirement
Run: First cycle
Allowed tools: Read, Write

---

What it does

Gathers the requirements for the current QA cycle and writes structured requirement documents to the requirements/ folder. On subsequent cycles, use /qa-impact instead.

---

Input sources

You can provide requirements in three ways:

Method	How
Jira	Paste Jira ticket URLs - the skill reads them via MCP if available
Paste	Paste raw requirement text directly into the chat
Questionnaire	Answer a guided set of questions interactively

---

Output files

One file per domain that has requirements:

requirements/
  requirements-shared.md    ← cross-domain context (environment, scope, risks)
  requirements-ui.md        ← UI-specific requirements
  requirements-api.md       ← API-specific requirements
  requirements-a11y.md      ← Accessibility-specific requirements
  requirements-perf.md      ← Performance-specific requirements

Files use dated sections - new versions prepend a new section while history is preserved below.

---

Versioning

## 2026-05-26

### Functional requirements
- Users can log in with email + password
- Password reset flow must send email within 30 seconds

### Non-functional requirements
- All pages must pass WCAG 2.1 AA
- API p95 latency must be under 300 ms

---
<!-- Previous versions below -->

## 2026-05-01
...

---

After requirements

Run /qa-plan to derive the test strategy.