Make Plan

1---2name: make-plan3description: 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.4---5 6# Make Plan7 8You are an ORCHESTRATOR. Create an LLM-friendly plan in phases that can be executed consecutively in new chat contexts.9 10## Delegation Model11 12Use 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.13 14### Subagent Reporting Contract (MANDATORY)15 16Each subagent response must include:171. Sources consulted (files/URLs) and what was read182. Concrete findings (exact API names/signatures; exact file paths/locations)193. Copy-ready snippet locations (example files/sections to copy)204. "Confidence" note + known gaps (what might still be missing)21 22Reject and redeploy the subagent if it reports conclusions without sources.23 24## Plan Structure25 26### Phase 0: Documentation Discovery (ALWAYS FIRST)27 28Before planning implementation, deploy "Documentation Discovery" subagents to:291. Search for and read relevant documentation, examples, and existing patterns302. Identify the actual APIs, methods, and signatures available (not assumed)313. Create a brief "Allowed APIs" list citing specific documentation sources324. Note any anti-patterns to avoid (methods that DON'T exist, deprecated parameters)33 34The orchestrator consolidates findings into a single Phase 0 output.35 36### Each Implementation Phase Must Include37 381. **What to implement** — Frame tasks to COPY from docs, not transform existing code39   - Good: "Copy the V2 session pattern from docs/examples.ts:45-60"40   - Bad: "Migrate the existing code to V2"412. **Documentation references** — Cite specific files/lines for patterns to follow423. **Verification checklist** — How to prove this phase worked (tests, grep checks)434. **Anti-pattern guards** — What NOT to do (invented APIs, undocumented params)44 45### Final Phase: Verification46 471. Verify all implementations match documentation482. Check for anti-patterns (grep for known bad patterns)493. Run tests to confirm functionality50 51## Key Principles52 53- Documentation Availability ≠ Usage: Explicitly require reading docs54- Task Framing Matters: Direct agents to docs, not just outcomes55- Verify > Assume: Require proof, not assumptions about APIs56- Session Boundaries: Each phase should be self-contained with its own doc references57 58## Anti-Patterns to Prevent59 60- Inventing API methods that "should" exist61- Adding parameters not in documentation62- Skipping verification steps63- Assuming structure without checking examples