Windsurf rules

1---
2name: elaborate-spec
3model: opus
4description: "Refine a rough idea into a clear, detailed specification through dialogue. Does not produce code. Use when user has a vague idea, wants to think through a feature before planning, or needs to turn \"I want X\" into a concrete spec."
5---
6 
7# Elaborate Spec
8 
9Turn a rough idea into a clear specification through focused dialogue. No code is written during this skill — the output is shared understanding and a refined problem statement.
10 
11> **HARD GATE** — Do NOT proceed with planning or implementation until the problem space is clearly understood. Success criteria, actors, and scope must be explicit before drafting a plan.
12 
13## Process
14 
15### 1. Listen first
16 
17Let the user describe their idea in their own words. Do not interrupt or redirect. Take notes on:
18- The core problem they're trying to solve
19- Who is affected (actors)
20- What success looks like to them
21- Any constraints they've already identified
22 
23### 2. Ask clarifying questions
24 
25Ask one question at a time. Work through these areas:
26 
27**Problem clarity**
28- What is the current behavior (or lack of behavior) that prompted this?
29- Who experiences this problem? How often?
30- What's the cost of not solving it?
31 
32**Solution boundaries**
33- What is explicitly IN scope?
34- What is explicitly OUT of scope?
35- Are there existing solutions (internal or external) this replaces or integrates with?
36 
37**Success criteria**
38- How will you know this is done?
39- What does the happy path look like end-to-end?
40- What are the key failure modes to handle?
41 
42**Constraints**
43- Any performance requirements?
44- Any compatibility constraints (existing APIs, data formats)?
45- Any non-negotiable implementation decisions already made?
46 
47### 2.5. Multiple Interpretations (HARD GATE)
48 
49> **HARD GATE** — If the request admits ≥2 valid interpretations, do NOT guess. You must list them and ask the user to choose before proceeding. Proceeding with unresolved ambiguity is a failure of integrity.
50 
51Present the options clearly:
52> "I see two ways to read this:
53> 1. [Interpretation A] — my recommendation because [reason]
54> 2. [Interpretation B]
55> Which is closer to what you mean?"
56 
57### 3. Surface hidden assumptions
58 
59Once the user has answered the main questions, probe for assumptions:
60- "You mentioned X — does that mean Y is also true?"
61- "What happens when Z fails?"
62- "Is this for internal users, external users, or both?"
63 
64### 4. Synthesize and confirm
65 
66Summarize your understanding in 3–5 bullet points aligned with [countable-story-format.md](../../docs/countable-story-format.md):
67- The problem (feeds into §1 Business narrative)
68- The solution and main flow (feeds into §5)
69- The key constraints and alternative flows (feeds into §6)
70- The success criteria (feeds into §17 Gherkin)
71- What's out of scope (feeds into §18)
72 
73Ask: "Is this an accurate summary? Anything missing or wrong?"
74 
75### 5. Write specs/planning-context.yaml
76 
77After the user confirms the summary in step 4, persist the key decisions:
78 
79```yaml
80# specs/planning-context.yaml — written by elaborate-spec; consumed by scope-work and slice-tasks
81feature_name: "<from step 1>"
82problem_statement: "<one paragraph>"
83constraints:
84  - "<constraint 1>"
85out_of_scope:
86  - "<excluded item 1>"
87key_decisions:
88  - decision: "<what was decided>"
89    rationale: "<why>"
90```
91 
92If `specs/planning-context.yaml` already exists, ask: `"Planning context from a prior session exists. Update it? [Y/n]"`. Overwrite on Y; leave unchanged on N.
93 
94### 6. Suggest next skill
95 
96Once the spec is clear, recommend the next step:
97- If domain model needs work → `model-domain`
98- If ready to plan → `plan-release` (creates epic capsules with `epic.yaml` + story `.md` + `-tasks.yaml`) then `plan-work` per story
99- If a spike is needed first → `spike-prototype`
100- If architecture decisions are needed → `deepen-architecture` or `grill-me`
101- If the plan depends on a specific library or API → `grill-me` in docs mode
102