/qa-onboard

Phase: 1 - Setup
Command: /qa-onboard
Run: Once per project
Allowed tools: Read, Write

---

What it does

Interviews the QA engineer with a short questionnaire (≈ 5 minutes) and writes dq-qa.config.json to the project root. All subsequent skills read this file on startup.

If dq-qa.config.json already exists, /qa-onboard detects it and asks which sections to update rather than starting from scratch.

---

Questions asked

Section	Questions
Project	What is the project name?
UI	Is UI testing in scope? What is the app's base URL? Should videos be recorded?
API	Is API testing in scope? What is the API base URL? Where is the OpenAPI/Swagger or GraphQL schema?
Accessibility	Is accessibility testing in scope? Which WCAG version and conformance level?
Performance	Is performance testing in scope? What are the p95 response time, error rate, and duration thresholds?

---

Output

Creates dq-qa.config.json in the project root:

{
  "project": { "name": "my-app" },
  "domains": {
    "ui": {
      "enabled": true,
      "baseUrl": "https://app.example.com",
      "recordVideo": true,
      "reportDir": "./qa-reports/ui"
    },
    "api": {
      "enabled": true,
      "baseUrl": "https://api.example.com",
      "schemaUrl": "https://api.example.com/swagger.json",
      "reportDir": "./qa-reports/api"
    },
    "accessibility": {
      "enabled": true,
      "jurisdiction": "NZ",
      "level": "AA",
      "reportDir": "./qa-reports/a11y"
    },
    "performance": {
      "enabled": true,
      "schemaUrl": "https://api.example.com/swagger.json",
      "thresholds": {
        "p99LatencyMs": 800,
        "okRequestPercent": 99
      },
      "reportDir": "./qa-reports/perf"
    }
  },
  "requirements": {
    "docsPath": "./requirements"
  }
}

Commit this file to your repository so the whole team shares the same configuration.

---

After onboarding

Run /qa-requirement (first cycle) or /qa-impact (subsequent cycles).

Full config reference → Configuration