qa-report

What this skill does

# Real-User QA Planner

Plan and document the deliverables that drive real-user QA execution — personas, journey maps, exploratory charters, persona/journey/tour test cases, regression suites, Figma fidelity validations, and user-impact bug reports.

## Required Reading Router

Match your task to the row. Read the listed files **in full before** producing the deliverable. They are not appendices — they are the templates and contracts the deliverable must conform to. Inline content in this SKILL.md is a pointer, not a substitute.

| Task                                              | MUST read                                                                                  |
| ------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| Defining personas (Step 3 — persona deliverable)  | `references/persona_test_cases.md` + `../qa-execution/references/user-personas.md`         |
| Mapping a journey (Step 3 — journey deliverable)  | `references/journey_test_plans.md` + `../qa-execution/references/journey-maps.md`          |
| Writing an exploratory charter (Step 3)           | `references/exploratory_charters.md` + `../qa-execution/references/exploratory-charters.md` |
| Planning a tour-driven test case (Step 4)         | `references/test_tours_catalog.md` + `../qa-execution/references/test-tours.md`            |
| Generating standard / functional / UI test cases  | `references/test_case_templates.md`                                                        |
| Generating CFR test cases (Step 4)                | `references/cfr_test_cases.md` + `../qa-execution/references/cfr-checks.md`                |
| Building a regression suite (Step 5)              | `references/regression_testing.md`                                                         |
| Validating against Figma (Step 6)                 | `references/figma_validation.md`                                                           |
| Filing a bug report (Step 7)                      | `references/bug_report_templates.md` + `assets/issue-template.md` + `../qa-execution/references/bug-severity-by-user-impact.md` |

## Reference Index

- `references/test_case_templates.md` — Test case variants for real-user QA: Standard, Functional, UI/Visual, Regression, Smoke, Persona, Journey, Charter, Tour, CFR. The Automation Metadata block parsed by `qa-execution`.
- `references/persona_test_cases.md` — TC-PERSONA-* template and persona attributes recording schema.
- `references/journey_test_plans.md` — TC-JOURNEY-* template and journey-driven plan structure.
- `references/exploratory_charters.md` — Charter planning template plus worked examples for common product surfaces.
- `references/test_tours_catalog.md` — Planning view of the test tour catalog. Each tour generates one TC-TOUR-*. Canonical tour definitions live in `../qa-execution/references/test-tours.md` (avoid drift).
- `references/cfr_test_cases.md` — TC-CFR-* template for usability / accessibility / perf-perception / compatibility / recoverability test cases.
- `references/regression_testing.md` — Journey-driven regression suite tiers (Smoke / Targeted / Full / Sanity), prioritization, automation tagging, pass/fail criteria.
- `references/figma_validation.md` — Figma MCP queries, spec → inspect → document workflow, responsive checks at 1280 / 768 / 375.
- `references/bug_report_templates.md` — Standard, UI/Visual, and User-Friction bug variants with full required-field sets. `assets/issue-template.md` is the minimum-viable subset bundled for in-skill use and shared with `qa-execution`.

## Required Inputs

- **qa-output-path** (optional): Directory where all QA artifacts are stored. When provided, create the directory if it does not exist. When omitted, use the current working directory. This path must match the same argument passed to `qa-execution` when both skills are used together.

## Shared Output Structure

All artifacts follow this directory layout, shared with `qa-execution`:

```
<qa-output-path>/qa/
├── test-plans/          # Test plan documents (journey plans, regression suites, persona docs)
│   └── charters/        # Charter drafts (CH-NN-*.md)
├── test-cases/          # Individual test case files (TC-*.md)
├── issues/              # Bug reports (BUG-*.md)
├── screenshots/         # Visual evidence and Figma comparisons
└── verification-report.md  # Generated by qa-execution
```

## Procedures

**Step 1: Resolve Output Directory**

1. If the user provided a `qa-output-path` argument, use that path.
2. Otherwise, default to the current working directory.
3. Create the `qa/` subdirectory under the resolved path, then `qa/test-plans/`, `qa/test-plans/charters/`, `qa/test-cases/`, `qa/issues/`, `qa/screenshots/`.

**Step 2: Identify the Deliverable Type**

Parse the user request to determine which deliverable to generate:

| Request Pattern | Deliverable | Output Path |
|-----------------|-------------|-------------|
| "Define personas for…" | Persona document | `test-plans/personas.md` |
| "Map the journey for…" | Journey map | `test-plans/<journey-slug>-map.md` |
| "Plan exploratory session for…" | Charter draft | `test-plans/charters/CH-<NN>-<slug>.md` |
| "Create test plan for…" | Test Plan (journey-centric) | `test-plans/<feature-slug>-test-plan.md` |
| "Generate test cases for…" | Test cases (TC-FUNC / TC-UI / TC-REG / SMOKE / TC-PERSONA / TC-JOURNEY / TC-TOUR / TC-CFR) | `test-cases/` |
| "Build regression suite…" | Journey-driven regression suite | `test-plans/<suite-name>-regression.md` |
| "Compare with Figma…" | Figma fidelity TC | `test-cases/TC-UI-*.md` |
| "Document bug…" | Bug report (user-impact framing) | `issues/BUG-*.md` |

**Step 3: Generate Test Plans (Journey-Centric)**

1. **STOP. Read `references/journey_test_plans.md` in full before drafting the plan.** That file owns the section structure, the Automation Metadata block, and the entry/exit criteria framed by user impact.
2. Generate a test plan document with these mandatory sections:
   - Executive summary with the user value the change delivers and the journey-level risks.
   - **Personas covered** (cite each from `../qa-execution/references/user-personas.md`).
   - **Journeys mapped** (cite each from `../qa-execution/references/journey-maps.md`; include abandonment paths).
   - **Charters planned** (mission + persona + tour + time-box for each).
   - **CFR scope** (which of the six CFR categories the change affects).
   - Test strategy and approach.
   - Automation strategy — which journeys should become E2E, which remain manual-only, which are blocked.
   - **Entry criteria** (all must hold before execution begins):
     - Build is reachable in a production-parity environment.
     - CI gate has run separately and is green (this skill does not run it — see `agent-output-audit`).
     - Test data and fixture state matches journey preconditions.
     - Personas, journeys, and charters are documented.
   - **Exit criteria** (all must hold before execution concludes):
     - Every P0 journey reached its goal observable.
     - Zero open `Blocks-Completion` or `Data-Loss` bugs on P0 journeys.
     - CFR pass completed on at least 2 journeys with no critical findings open.
     - Automation follow-up registered for every `Missing` or `Blocked` automation annotation.
   - **Retesting vs Regression** distinction:
     - **Retesting** — re-validates the fix of a specific reported defect. Scope is the BUG and its narrow reproduction.
     - **Regression** — validates that a change did not break unrelated journeys. Scope is the journey-driven suite.
   - Risk assessment table (Risk, Probability, User-Impact, Mitigation).
   - Timeline and deliverables.
3. Write the plan to `<qa-output-path>/qa/test-plans/<feature-slug>-test-plan.md`.

**Step 4: Generate Test Cases**

1. **STOP. Read `references/test_case_templates.md` in full before writing any test case.** Variant selection (Function