01
What this skill does
Use this skill when the user requests planning, a saved plan file, or architecture and tradeoff analysis. It creates an editable Markdown plan, researches concrete code references, resolves material questions, and maintains buildable todos. Planning-only requests stop before implementation; plan-and-build requests continue within existing authorization. Complexity or multiple files alone do not introduce an approval gate. Use `grill-me` for a requested interview or unresolved user decisions that benefit from one.
02
When to use it
- 01Planning multi-file implementation, architecture, routing, data-flow, or tradeoff-heavy work.
- 02Maintaining a live Markdown plan document with file references, code references, and checkbox todos.
- 03Invoking `grill-me` for an interview or material unresolved user decisions.
- 04Holding a strict boundary around dirty worktrees, migrations, settings, deployment, generated code, or other high-blast-radius surfaces.
- 05Building all or selected todos within existing authorization, or delivering a planning-only result.
03
How it works
- 01
Resolve whether the request is planning-only or also authorizes implementation, then create or reuse the Markdown plan file 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
Pressure-test assumptions with evidence; invoke `grill-me` when an interview is requested or material user decisions remain unresolved.
- 06
Validate and summarize the plan, then deliver the planning-only result or execute the authorized todos with relevant checks and required repository gates.
04
What you get back
- 01A concrete Markdown plan with code references, editable todos, and an accurate authorization state.
- 02`grill-me` transcript and planning-ready outcome paths when a pressure-test was needed.
- 03Focused clarification questions when ambiguity would change the plan.
- 04A build-from-plan handoff or authorized implementation with proportionate validation.
05
Important boundaries
- 01During planning-only work, plan files and `grill-me` logs/outcomes are the only allowed writes; do not edit implementation, install packages, start services, or mutate Git state.
- 02Do not hide unresolved product, data, safety, or architecture assumptions inside the final plan.
- 03Do not build without rereading the plan and resolving authorization for all or selected todos; do not request approval again for already authorized work.
06