Windsurf rules

1---
2name: grill-with-docs
3model: opus
4description: "Doc-grounded variant of grill-me — stress-tests plan assumptions by fetching and citing real library or API documentation. Every challenge must cite a real URL. Use when the plan depends on a specific library or external API."
5---
6 
7# Grill With Docs
8 
9> **Use this vs grill-me:** `grill-with-docs` is the doc-grounded variant of `grill-me`. Use it when the plan relies on external libraries or APIs and every challenge must be grounded in and cite a real documentation URL. Use `grill-me` for context-only assumption surfacing without fetching docs.
10 
11> **HARD GATE** — Every challenge must cite a real documentation URL. No hallucinated APIs.
12 
13## Process
14 
151. Read the plan or design under test (`specs/release-plan.yaml + epic shards`, INTERFACE-OPTIONS.md, etc.).
162. List assumptions that depend on external libraries or APIs.
173. For each assumption: fetch or quote official docs; challenge with "docs say X, plan says Y."
184. Resolve or update the plan inline; unresolved items block `plan-work`.
19 
20## Docs mode rules
21 
22- Cite URL + quoted snippet (method name, parameter, version).
23- If docs contradict the plan, plan loses until updated.
24- Prefer official docs over blog posts.
25 
26## Facts vs. Decisions Boundary
27 
28Distinguish between **facts** and **decisions**:
29- **Facts** — things discoverable by reading docs, checking APIs, or exploring the codebase. Do not ask the user to confirm facts; find them yourself.
30- **Decisions** — choices that require user input (trade-offs, preferences, priorities). Always present options and ask the user to choose.
31 
32Never "grill yourself" — if the answer is in the docs, go fetch it. Only ask questions where the user's judgment is needed.
33 
34## Confirmation Gate
35 
36> **HARD GATE** — Do NOT enact the plan or generate specifications until the user explicitly confirms shared understanding. Wait for explicit approval (e.g., "looks good", "confirmed", "proceed") before transitioning to any implementation, spec-writing, or task-slicing step.
37 
38## Verify
39 
40→ verify: `test -f skills/grill-with-docs/SKILL.md && test -f skills/grill-with-docs/REFERENCE.md`
41 
42See [REFERENCE.md](REFERENCE.md) for question templates.
43 
44 
45<!-- story: e03s01 -->
46 
47---
48 
49# Grill With Docs — Question templates
50 
51- "Docs at [URL] show signature `foo(bar?: Baz)`. Your plan calls `foo(bar, baz)` — which is correct?"
52- "The changelog at [URL] deprecates X in v3. Your plan still uses X — migrate or pin version?"
53- "Error handling in [URL] throws `NetworkError`. Your plan catches `Error` only — is that sufficient?"
54