← ClaudeAtlas

planning-workflowlisted

Jeffrey Emanuel's comprehensive markdown planning methodology for software projects. The 85%+ time-on-planning approach that makes agentic coding work at scale. Includes exact prompts used.
aiskillstore/marketplace · ★ 329 · AI & Automation · score 79
Install: claude install-skill aiskillstore/marketplace
# Planning Workflow — The Foundation of Agentic Development > **Core Philosophy:** "Planning tokens are a lot fewer and cheaper than implementation tokens." > > The models are far smarter when reasoning about a detailed plan that fits within their context window. This is the key insight behind spending 80%+ of time on planning. --- ## Why Planning Matters Before burning tokens with a big agent swarm: - **Measure twice, cut once** — becomes "Check your plan N times, implement once" - A very big, complex markdown plan is still shorter than a few substantive code files - Front-loading human input in planning enables removing yourself from implementation - The code will be written ridiculously quickly when you start enough agents with a solid plan --- ## The Planning Process (Overview) ``` ┌──────────────────────────────────────────────────────────────┐ │ 1. INITIAL PLAN (GPT Pro / Opus 4.5 in web app) │ │ └─► Explain goals, intent, workflows, tech stack │ ├──────────────────────────────────────────────────────────────┤ │ 2. ITERATIVE REFINEMENT (GPT Pro Extended Reasoning) │ │ └─► 4-5 rounds of revision until steady-state │ ├──────────────────────────────────────────────────────────────┤ │ 3. MULTI-MODEL BLENDING (Optional but recommended) │ │ └─► Gemini3 Deep Think, Grok4 Heavy, Opus 4.5 │ │ └─► GPT Pro as final arbiter │ ├─────────────────────────────────────────────