Cursor rule

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