Quick Start

Get from zero to a complete QA cycle in minutes.

---

1. Install the plugin

Install dq-awesomeqa in your coding agent first:

• Claude Code: Claude Installation
• GitHub Copilot (VS Code): Copilot Installation
• Gemini CLI: Gemini Installation

2. Start the guided journey

Open your project in your coding agent session and run:

/qa-init

/qa-init walks you through every phase in order, enforces gates between phases, and lets you choose which domains to include. This is the recommended entry point.

---

Guided flow overview

/qa-init
   │
   ├─ "Have you run qa-setup on this machine?"
   │     No  → runs /qa-setup  (installs a11y-cli + dq-nbomber)
   │     Yes → skips
   │
   ├─ "Does dq-qa.config.json exist for this project?"
   │     No  → runs /qa-onboard  (5 min interview → writes config)
   │     Yes → skips
   │
   ├─ "Which domains are in scope for this cycle?"
   │     [ ] UI   [ ] API   [ ] Accessibility   [ ] Performance
   │
   ├─ Runs planning:  /qa-requirement  →  /qa-plan
   │
   ├─ Runs design:    (only selected domains)
   │     /qa-api  /qa-ui  /qa-a11y  /qa-perf  →  /qa-coverage
   │
   ├─ Phase gate: confirm before execution
   │
   ├─ Runs execution: /qa-exec
   │
   └─ Runs closure:   /qa-triage  →  /qa-coverage  →  /qa-report

---

Running individual skills

Experienced users can invoke skills directly without going through /qa-init:

/qa-api          # just the API test plan
/qa-perf         # just the load test config
/qa-exec         # execute whatever is already planned

Read qa-plan.md first

Design skills (/qa-api, /qa-ui, /qa-a11y, /qa-perf) always read qa-plan.md before acting. Running them without a plan may produce out-of-scope work.

---

Single-domain cycle example

API only - useful for a backend-only sprint:

/qa-requirement   # document the sprint requirements
/qa-plan          # derive strategy (select API domain only)
/qa-api           # build the API test plan
/qa-coverage      # gap check
/qa-exec          # execute
/qa-triage        # triage failures (if any)
/qa-report        # summary

---

Subsequent cycles

On the second and later cycles, replace /qa-requirement with /qa-impact:

/qa-impact        # record what changed since last cycle
/qa-plan          # update strategy for changed requirements
# ... rest of the flow unchanged

/qa-impact compares new requirements to the previous cycle, flags only the domains that need re-running, and updates qa-plan.md in place (with version history preserved).