
Planning Workflow
Jeffrey Emanuel's battle-tested approach to planning before you write a single line of code. The core idea is spending 80%+ of your time iterating on a massive markdown plan using GPT Pro Extended Reasoning, then converting it into self-contained task "beads" for Claude Code to execute. You'll run 4-5 rounds of refinement using exact prompts provided, optionally blending competing plans from Gemini, Grok, and Opus. The methodology produces 3,500+ line plans that include workflows, architecture justifications, and dependency chains. It's methodical to the point of feeling tedious, but the claim is you save 10x the time during implementation because agents have complete context without needing to ask questions.
- skills.sh installs
- 154
- GitHub stars
- 73
- last updated
- Aug 21, 2026
Install
$ npx -y skills add dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations --skill planning-workflow --agent claude-codeInstalls into .claude/skills of the current project.
Files
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.
Outcome — When This Skill Has Delivered
You have a usable plan when all of the following hold:
Sponsors
Details
- Repository
- github.com/dicklesworthstone/agent_flywheel_clawdbot_skills_and_integrations
- Categories
- AI & Agent Building, Productivity & Planning, Automation & Workflows
- First seen
- Jun 3, 2026