01
What this skill does
Use this skill when work is complex, ambiguous, risky, or broad enough that premature edits would create churn or damage user intent. It mirrors Cursor's Plan Mode loop: create or update a disk-backed editable plan file, research the codebase into file and code references, ask focused clarification questions, maintain buildable todos, invoke `grill-me` for non-trivial pressure-testing, validate the plan artifact, and build only from the approved plan.
02
When to use it
- SignalPlanning multi-file implementation, architecture, routing, data-flow, or tradeoff-heavy work.
- SignalMaintaining a live Markdown plan document with file references, code references, and checkbox todos.
- SignalInvoking `grill-me` to pressure-test meaningful assumptions, risks, failure modes, and rollout or rollback edges.
- SignalHolding a strict boundary around dirty worktrees, migrations, settings, deployment, generated code, or other high-blast-radius surfaces.
- SignalBuilding all or selected todos only after the user approves the plan.
03
How it works
- 01
Create or reuse the Markdown plan file immediately and cite its path.
- 02
Research only what is needed, then update the plan with concrete file paths, code references, constraints, and open questions.
- 03
Ask clarifying questions when decisions would change the plan, and update the file after each answer.
- 04
Maintain editable checkbox todos that can be selected and built from later.
- 05
Invoke `grill-me` before approval when the plan has meaningful assumptions, tradeoffs, failure modes, or scope edges.
- 06
Validate the plan artifact, summarize it in chat, and wait for approval before building from all or selected todos.
04
What you get back
- SignalA concrete approval-gated Markdown plan file with file/code references and editable todos.
- Signal`grill-me` transcript and planning-ready outcome paths when a pressure-test was needed.
- SignalFocused clarification questions when ambiguity would change the plan.
- SignalA clean build-from-plan handoff after approval, including promised validation steps.
05
Important boundaries
- SignalDo not edit implementation files, stage commits, install packages, start services, or run write-oriented scripts while planning; plan files and `grill-me` logs/outcomes are the only allowed writes.
- SignalDo not hide unresolved product, data, safety, or architecture assumptions inside the final plan.
- SignalDo not build without rereading the plan file and confirming whether approval covers all todos or only selected todos.
06