Windsurf rules

1---
2name: change-request
3model: sonnet
4description: "Add a new requirement or reorder epics by WSJF against specs/release-plan.yaml and epic capsule directories. Modes Add and Reorder. Use when a new requirement arrives mid-release or the plan needs prioritization."
5---
6 
7# story: e45s29
8# story: e20s01
9 
10# Change Request
11 
12> **HARD GATE** — `specs/release-plan.yaml` must exist before running either mode. If it doesn't, run `plan-release` first.
13>
14> → verify: `test -f specs/release-plan.yaml`
15 
16Two modes. State which one you want or the skill will ask.
17 
18## Mode A — Add
19 
20Intake a new requirement mid-flight without disrupting work in progress.
21 
221. **Capture**: What is the change? What problem does it solve?
232. **Locate**: Which existing stories in `specs/epics/` does it affect or replace?
243. **Draft**: Add story + `tasks[]` with Gherkin-style AC in epic YAML (each task has `verify`). Tag requirement deltas: `ADDED` / `MODIFIED` / `REMOVED` / `RENAMED` with before/after for non-`ADDED` changes (e45s29).
254. **Place**: Append story under existing epic capsule, or create `specs/epics/eNN-slug.yaml` and register in `release-plan.yaml` `epics[]`.
265. **Score**: Compute WSJF; note if it outranks in-progress work.
27 
28→ verify: `grep -c 'stories:' specs/epics/*/epic.yaml`
29 
30## Mode B — Reorder
31 
32Value-engineering pass over the full release using WSJF.
33 
34See [REFERENCE.md](REFERENCE.md) for the full WSJF scoring rubric.
35 
361. **Score** each epic/story: BV + TC + RR / Job Size.
372. **Re-sort** `release-plan.yaml` `epics[]` and per-epic `wsjf` fields.
383. **Flag cut candidates**: WSJF < 1.5.
394. **Update** `specs/release-plan.yaml` and epic `wsjf` keys with rationale.
405. **Report** the delta.
41 
42→ verify: `grep -c 'wsjf' specs/release-plan.yaml specs/epics/*/epic.yaml`
43 
44## Conversational Mode
45 
46If the user's request is in natural language and does not match the structured format of Mode A or Mode B, enter Conversational Mode to extract the change parameters through interactive dialogue.
47 
48### 5-Step Flow
49 
501. **Capture**: Parse the natural-language request for what, why, and where. Ask at most 3 clarifying questions before drafting.
512. **Locate**: Identify which epic or capability in `specs/epics/` the request affects or replaces.
523. **Draft**: Present a structured draft of the proposed story and tasks for user confirmation.
534. **Score**: Estimate the WSJF score and explain the calculation so the user understands the priority.
545. **Place**: Confirm the final epic placement with the user before writing files.
55 
56## After either mode
57 
58Run `bash scripts/sync-status-from-epics.sh`. Suggest `plan-work` or `build-epic` for the top-ranked unstarted story.
59 
60---
61 
62# WSJF Scoring Reference
63 
64Weighted Shortest Job First: **WSJF = (Business Value + Time Criticality + Risk Reduction) / Job Size**
65 
66All dimensions scored 1–10 using a Fibonacci-like scale: 1, 2, 3, 5, 8, 10.
67 
68## Business Value
69 
70| Score | Meaning |
71|-------|---------|
72| 10 | Core revenue path, legal requirement, blocking launch |
73| 8  | Significant user value, major pain point removed |
74| 5  | Notable improvement, medium user segment affected |
75| 3  | Nice-to-have, minor convenience |
76| 1  | Cosmetic or speculative |
77 
78## Time Criticality
79 
80| Score | Meaning |
81|-------|---------|
82| 10 | Hard deadline (regulatory, contract, launch date) |
83| 8  | Competitive window closing, partner dependency |
84| 5  | Would delay next milestone if deferred |
85| 3  | Flexible, can slip one sprint |
86| 1  | No urgency |
87 
88## Risk Reduction (or Opportunity Enablement)
89 
90| Score | Meaning |
91|-------|---------|
92| 10 | Eliminates critical architectural risk or enables a new capability |
93| 8  | Reduces a known failure mode or unblocks high-value work |
94| 5  | Moderate risk mitigation or enablement |
95| 3  | Low risk reduction |
96| 1  | No risk relevance |
97 
98## Job Size (effort denominator — larger = lower WSJF)
99 
100| Score | Meaning |
101|-------|---------|
102| 1  | Hours |
103| 2  | 1 day |
104| 3  | 2–3 days |
105| 5  | 1 week |
106| 8  | 2 weeks |
107| 10 | 1 month+ |
108 
109## Cut threshold
110 
111Stories with WSJF < 1.5 are cut candidates: high effort, low combined value.
112 
113## Example
114 
115Story: "Add OAuth login"
116- Business Value: 8 (removes major sign-up friction)
117- Time Criticality: 5 (Q3 launch nice, not hard)
118- Risk Reduction: 3 (minor security improvement)
119- Job Size: 5 (one week)
120 
121WSJF = (8 + 5 + 3) / 5 = **3.2** — healthy, implement early.
122