Windsurf rules

1---
2name: plan-tests
3model: opus
4description: "Design a risk-scaled test architecture for an epic before implementation begins. Produces prioritized scenarios, test level distribution, and fixture plans based on TEA and bigpowers principles."
5---
6 
7# Plan Tests
8 
9> **Spine position:** Between `slice-tasks` and `plan-work` for epics with `risk: P0|P1`. Optional (can be waived in `state.yaml`) for P2/P3.
10 
11Bridges the gap between slicing and planning by systematically designing the test suite as a first-class system. Produces `specs/tech-architecture/eNN-TEST_PLAN_LATEST.md`.
12 
13## Pre-flight
14- Read `specs/epics/eNN-*/` story list.
15 
16## Core Workflow
171. **Analyze Epic**: Read sliced stories in the active epic capsule.
182. **Risk Assessment**: Map behaviors to P0–P3 risk tiers.
193. **Level Strategy**: Classify each scenario (Unit, Integration, E2E).
204. **Fixture Design**: Plan factories, network intercepts, mocks (see REFERENCE.md).
215. **NFR Plan**: Define verifiable commands for Non-Functional Requirements. Skip if `--lite`.
226. **Publish**: Generate `specs/tech-architecture/eNN-TEST_PLAN_LATEST.md`.
23 
24## Hard Gates & Guardrails
25- **DO NOT** write test code or production code during this skill.
26- Scenario ID format MUST be: `SC-eNNsYY-P{0|1|2|3}-NN`.
27- `plan-work` MUST reference these scenario IDs in its §17 Gherkin acceptance criteria.
28- Default to pushing tests to the lowest possible level.
29 
30## Execution Modes
31- `$bmad plan-tests`: Standard execution.
32- `$bmad plan-tests --lite`: Skips NFRs and complex fixture planning.
33 
34## Verify
35 
36→ verify: `test -f specs/tech-architecture/e32-TEST_PLAN_LATEST.md`
37 
38## Handoff
39 
40Gate: READY -> next: plan-work
41Writes: state.yaml handoff.next_skill = plan-work
42 
43---
44 
45# Plan Tests — Reference
46 
47## Test Plan Template (`specs/tech-architecture/eNN-TEST_PLAN_LATEST.md`)
48 
49```markdown
50# Test Design: [eNN-slug]
51 
52## 1. Risk Matrix & Scenarios
53| Scenario ID | Behavior Description | Risk | Test Level | Target File/Module |
54|-------------|----------------------|------|------------|--------------------|  
55| SC-P0-01    | Primary checkout     | P0   | Integration | checkout.spec.ts  |
56 
57## 2. Fixture Architecture & Isolation
58- Data Factories: (e.g. UserFactory)
59- Network Intercepts: (e.g. MSW handlers)
60- Database State: (e.g. in-memory SQLite)
61 
62## 3. NFR Verification
63| NFR Type | Requirement | Verification Command |
64|----------|-------------|----------------------|
65| Perf     | < 200ms     | `npm run test:perf`  |
66 
67## 4. Out of Scope
68- [Explicitly excluded testing areas]
69```
70 
71## Fixture Planning Guidance
72 
73- **Data Factories**: Prefer factory functions over manual object construction.
74- **Network Intercepts**: For frontend integration tests, use tools like Mock Service Worker (MSW) to intercept and mock HTTP requests.
75- **Database State**: For backend tests, use a clean database state per test or an in-memory database to ensure isolation.
76