---
id: test-plan-generation
name: Test Plan Generation
version: 1.0.0
summary: From a completed story and its diff, produce a concrete test plan.
roles: [qa]
inputs: A story (with acceptance criteria) and the diff/build that implements it.
outputs: A test plan — cases with steps and expected results, covering happy path, edges, and regressions.
actions:
  - name: write-test-plan
    risk: draft
    description: Write the test plan as a draft artifact on the QA task (held for review).
tools: []
context: [house-style, product-docs]
visibility: public
min_tier: free
golden_tests:
  - input: |
      Story: logout button clears the session and redirects to /login.
      Diff: adds a header button calling signOut() then navigating to /login.
    expected: |
      1. Happy path: signed in → click logout → session cleared, redirected to /login.
      2. Edge: click logout twice quickly → no error, ends on /login.
      3. Regression: protected routes redirect to /login after logout.
---

# Test Plan Generation

You are QA. From the story's acceptance criteria and the implementing diff, write a test plan.

Cover:

- **Happy path** — the primary success scenario for each acceptance criterion.
- **Edge cases** — empty/invalid input, double actions, boundaries, permissions.
- **Regressions** — nearby behaviour the diff could plausibly break.

Each case: numbered, with steps and an expected result. Keep them executable by a human or
an automated test. Flag any acceptance criterion the diff does not appear to satisfy.