- name
- make-plan
- description
- Create a detailed, phased implementation plan with documentation discovery. Use when asked to plan a feature, task, or multi-step implementation — especially before executing with do.
Make Plan
You are an ORCHESTRATOR. Create an LLM-friendly plan in phases that can be executed consecutively in new chat contexts.
Delegation Model
Use subagents for fact gathering and extraction (docs, examples, signatures, grep results). Keep synthesis and plan authoring with the orchestrator (phase boundaries, task framing, final wording). If a subagent report is incomplete or lacks evidence, re-check with targeted reads/greps before finalizing.
Subagent Reporting Contract (MANDATORY)
Each subagent response must include:
- Sources consulted (files/URLs) and what was read
- Concrete findings (exact API names/signatures; exact file paths/locations)
- Copy-ready snippet locations (example files/sections to copy)
- "Confidence" note + known gaps (what might still be missing)
Reject and redeploy the subagent if it reports conclusions without sources.
Plan Structure
Primary Goal (top of the document, before Phase 0)
Every plan opens with a Primary goal section: one or two sentences describing the user-visible outcome the plan exists to produce — not the mechanism. Write it so a reader with no context knows what "done" looks like.
- Good: "A paying user whose observer stops working finds out within one session and is told the one thing to do about it."
- Bad: "Add a 6-code error taxonomy to the gateway."
Then, directly under every phase title (Phase 0 through the final verification phase), add a short paragraph:
How this serves the primary goal: …
If you cannot write that paragraph honestly for a phase, the phase does not belong in the plan. This is the scope test.
Phase 0: Documentation Discovery (ALWAYS FIRST)
Before planning implementation, deploy "Documentation Discovery" subagents to:
- Search for and read relevant documentation, examples, and existing patterns
- Identify the actual APIs, methods, and signatures available (not assumed)
- Create a brief "Allowed APIs" list citing specific documentation sources
- Note any anti-patterns to avoid (methods that DON'T exist, deprecated parameters)