Make Plan

About

The make-plan skill turns an orchestrator agent into a planner that writes LLM-friendly phased implementation plans grounded in real documentation rather than assumed APIs. Phase 0 always deploys Documentation Discovery subagents to read docs, examples, and existing patterns, then consolidate an Allowed APIs list with anti-patterns before any implementation phases are authored. Each later phase frames copy-from-docs tasks with specific file and line references, verification checklists, and guards against invented methods or undocumented parameters. Subagents must follow a reporting contract listing sources consulted, concrete findings, copy-ready snippet locations, and confidence gaps; the orchestrator rejects conclusions without evidence. The final verification phase checks implementations against documentation, greps for known bad patterns, and runs tests. Plans are structured so each phase can run in a new session with self-contained references, pairing naturally with the sibling do skill for execution. Use when asked to plan a feature, multi-step task, or implementation before running do.

• Phase 0 Documentation Discovery is mandatory before any implementation planning begins.
• Subagent reporting contract requires sources, concrete findings, snippet locations, and confidence gaps.
• Each phase directs copy-from-docs tasks with file references instead of vague migration goals.
• Anti-pattern guards block invented APIs, undocumented parameters, and skipped verification.
• Final verification phase greps bad patterns and runs tests before declaring the plan complete.