Windsurf rules

1---
2name: plan-release
3model: sonnet
4description: "RELEASE-INDEX BUILDER — Sequence elaborated epics into specs/release-plan.yaml with WSJF ordering and BCP baselines. NOT a planning-spine substitute: it does not scope work (scope-work) or write story tasks (plan-work). Use after elaborate-spec when the user wants a versioned release index of epics."
5---
6 
7# Plan Release
8 
9> **HARD GATE** — Do NOT run this skill unless `elaborate-spec` has produced a clear spec or the user has already defined the feature in detail. If the problem is still fuzzy, run `elaborate-spec` first.
10> **HARD GATE** — `specs/product/SCOPE_LATEST.yaml` (or legacy `specs/product/SCOPE_LATEST.yaml`) must exist. If missing, run `scope-work` first.
11 
12Synthesize the conversation context into `specs/release-plan.yaml` (index) and shard detail under `specs/epics/`. No new interview — only clarify if something is genuinely ambiguous.
13 
14## Outputs
15 
16| File | Content |
17|------|---------|
18| `specs/release-plan.yaml` | `release.version`, semver bump hint, WSJF-ordered epic list with `id`, `capsule_dir`, `wsjf`, `bcps` — **no story status** |
19| `specs/epics/eNN-<slug>/epic.yaml` | Epic manifest: `id`, `title`, `wsjf`, `total_bcps`, `status`, `stories[]` list |
20| `specs/epics/eNN-<slug>/eNNsYY-<slug>.md` | Story spec in [countable-story-format.md](../../docs/countable-story-format.md) with 20 sections and Gherkin acceptance criteria |
21| `specs/epics/eNN-<slug>/eNNsYY-tasks.yaml` | Decoupled task checklist with `verify:` commands per task |
22| `specs/execution-status.yaml` | Flat key-value store for story status (`eNNsYY: todo`) |
23 
24## Epic Capsule Structure
25 
26All epics use capsule directories (no flat/folder distinction):
27 
28```
29specs/epics/e01-auth-system/
30├── epic.yaml              # Epic manifest
31├── adr/                   # Epic-local ADRs (created lazily)
32├── e01s01-login.md        # Story spec (countable-story-format)
33├── e01s01-tasks.yaml      # Decoupled task checklist
34├── e01s02-jwt.md          # Story spec
35└── e01s02-tasks.yaml      # Decoupled task checklist
36```
37 
38**Rationale:** Capsule dirs achieve change isolation (C9), enable archive pruning (C2/C6), and enforce SRP by decoupling spec `.md` from execution `-tasks.yaml` (C1).
39 
40## Process
41### 1. Draft epics and stories
42 
43From the conversation context, define:
44- **Epics** — `e01`, `e02`, … (stable IDs; WSJF order in `release-plan.yaml` only)
45- **Stories** — `e01s01`, `e01s02`, … with Gherkin acceptance criteria
46 
47WSJF-sort epics: score = (Business Value + Time Criticality + Risk Reduction) / Job Size. Highest score first.
48 
49> **Security risk boost:** If an epic's `specs/security/epics/<id>/THREAT_MODEL.md` identifies HIGH or CRITICAL risk, add +2 to the WSJF numerator (BV + TC + RR + 2) to reflect the urgency of addressing security concerns before they ship. Document the boost in the epic's note field in release-plan.yaml.
50### 2. Write acceptance criteria (Gherkin)
51 
52For each story, write at least one happy-path and one edge-case scenario (countable format §17 if maturity ≥ 3).
53### 3. Write tasks with verify commands
54 
55Every task must have a `verify:` command. No verify command = not a task.
56### 4. Save specs/release-plan.yaml
57 
58> **Do NOT hand-track the real version.** semantic-release decides it at merge. `version` here is a
59> non-authoritative mirror/label only — read the real number with `gh release view`. Set `bump_hint`
60> (the expectation), not a number you intend to enforce.
61 
62```yaml
63release:
64  version: "2.29.0"         # mirror of next expected tag, NOT authoritative — gh release view wins
65  codename: "Feature Name"
66  status: planning          # planning | in_progress | released
67  semantic_release: true
68  bump_hint: minor          # patch | minor | major — CI decides at merge
69epics:
70  - id: e01
71    title: Auth System
72    wsjf: 4.5
73    capsule_dir: epics/e01-auth-system
74  - id: e02
75    title: User Profile
76    wsjf: 3.8
77    capsule_dir: epics/e02-user-profile
78```
79### 5. Save epic manifest (`epic.yaml`)
80 
81Each epic capsule directory contains an `epic.yaml` manifest:
82 
83```yaml
84id: e01
85title: Auth System
86wsjf: 4.5
87total_bcps: 8
88status: in_progress
89stories:
90  - id: e01s01
91    title: Login
92    bcps: 3
93    status: todo
94    spec: e01s01-login.md
95    tasks: e01s01-tasks.yaml
96  - id: e01s02
97    title: JWT Token Management
98    bcps: 5
99    status: todo
100    spec: e01s02-jwt.md
101    tasks: e01s02-tasks.yaml
102```
103### 6. Save story specs (countable-story-format .md)
104 
105Each story becomes a standalone `.md` file following [countable-story-format.md](../../docs/countable-story-format.md). Minimum: maturity 3 (Countable) with all 20 sections present. Acceptance criteria in §17 use Gherkin scenarios.
106### 7. Save decoupled task files (`-tasks.yaml`)
107 
108Each story has a decoupled `-tasks.yaml` with implementation steps:
109 
110```yaml
111story_id: e01s01
112title: Login
113status: todo
114bcps: 3
115tasks:
116  - id: 1
117    description: "Add login form component tests"
118    verify: "npm test -- login-form.test.tsx"
119    status: todo
120  - id: 2
121    description: "Implement login form with validation"
122    verify: "npm test -- login-form.test.tsx"
123    status: todo
124```
125 
126> **HARD GATE** — Every task MUST have a runnable `verify:` command. No `verify:` = not a task.
127 
128→ verify: `bash scripts/validate-specs-yaml.sh`
129### 7b. Generate bug registry summary
130 
131Read `specs/bugs/registry.yaml` and add a `bugs:` section to `release-plan.yaml` with totals by status (`fixed`, `deferred`, `wontfix`, `open`): `bugs: { total: N, fixed: N, deferred: N, wontfix: N, registry: specs/bugs/registry.yaml }`.
132 
133### 8. Sync execution status
134 
135```bash
136bash scripts/sync-status-from-epics.sh
137```
138### 9. Snapshot on planning close (optional)
139 
140Copy to `specs/product/snapshots/release-<version>/` when the user approves the plan.
141### 10. Suggest next steps
142 
143- Run `assess-impact` before `plan-work` for any story touching existing modules.
144- Run `plan-work` per story for detailed steps inside the epic shard.
145- Run `change-request` if a new requirement arrives mid-flight.
146