01
What this skill does
Use this skill when a plan, design, rollout, or technical direction needs to be stress-tested before implementation. It asks one question at a time, keeps a Markdown Q&A log in sync, and finalizes a planning-ready outcome when the decision is concrete enough for another engineer to execute.
02
When to use it
- 01Turning vague plans into explicit success criteria, non-goals, and phase boundaries.
- 02Finding hidden failure modes, irreversible decisions, and stakeholder costs.
- 03Producing a planning-ready record from a live Q&A session.
03
How it works
- 01
Start or resume the local grilling log for the session.
- 02
Ask the highest-leverage unresolved question instead of collecting shallow preferences.
- 03
Cover objective, scope, stakeholders, alternatives, risks, validation, rollout, and rollback where relevant.
- 04
Keep the transcript synchronized with the conversation as the plan sharpens.
- 05
Finalize an outcome Markdown file and remove the active session pointer.
04
What you get back
- 01A live Q&A transcript.
- 02A finalized planning-ready outcome document.
- 03Explicit assumptions, tradeoffs, risks, and open decisions.
05
Important boundaries
- 01Ask one question at a time.
- 02Do not accept vague answers as final planning input.
- 03Do not leave the active session pointer behind after finalization.
06