Cursor rule

1---
2description: "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."
3alwaysApply: false
4---
5 
6# Grill With Docs
7 
8> **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.
9 
10> **HARD GATE** — Every challenge must cite a real documentation URL. No hallucinated APIs.
11 
12## Process
13 
141. Read the plan or design under test (`specs/release-plan.yaml + epic shards`, INTERFACE-OPTIONS.md, etc.).
152. List assumptions that depend on external libraries or APIs.
163. For each assumption: fetch or quote official docs; challenge with "docs say X, plan says Y."
174. Resolve or update the plan inline; unresolved items block `plan-work`.
18 
19## Docs mode rules
20 
21- Cite URL + quoted snippet (method name, parameter, version).
22- If docs contradict the plan, plan loses until updated.
23- Prefer official docs over blog posts.
24 
25## Facts vs. Decisions Boundary
26 
27Distinguish between **facts** and **decisions**:
28- **Facts** — things discoverable by reading docs, checking APIs, or exploring the codebase. Do not ask the user to confirm facts; find them yourself.
29- **Decisions** — choices that require user input (trade-offs, preferences, priorities). Always present options and ask the user to choose.
30 
31Never "grill yourself" — if the answer is in the docs, go fetch it. Only ask questions where the user's judgment is needed.
32 
33## Confirmation Gate
34 
35> **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.
36 
37## Verify
38 
39→ verify: `test -f skills/grill-with-docs/SKILL.md && test -f skills/grill-with-docs/REFERENCE.md`
40 
41See [REFERENCE.md](REFERENCE.md) for question templates.
42 
43 
44<!-- story: e03s01 -->
45 
46---
47 
48# Grill With Docs — Question templates
49 
50- "Docs at [URL] show signature `foo(bar?: Baz)`. Your plan calls `foo(bar, baz)` — which is correct?"
51- "The changelog at [URL] deprecates X in v3. Your plan still uses X — migrate or pin version?"
52- "Error handling in [URL] throws `NetworkError`. Your plan catches `Error` only — is that sufficient?"
53