How I Plan Complex Projects With Claude Code (Open-Source)

My Plans Kept Failing at the Worst Possible Moment

Three months into using Claude Code full-time, I noticed a pattern. My plans looked solid on paper. Clear phases, reasonable timelines, specific outcomes. Then halfway through execution, something would surface that invalidated the entire approach. A dependency I did not check. An assumption that was wrong. A simpler solution I never considered.

This happened over a hundred times before I tracked it. Not a hundred plans total - a hundred plans where the critical insight arrived AFTER I started building. The fix was never in the plan itself. It was in what happened before the plan.

Want the complete system? The free 3-pattern guide covers memory, delegation, and planning - the foundations behind my Claude Code setup.

The Root Cause: Discovery Happens Too Late

Traditional planning follows a straight line: Goal, Approach, Steps, Execute. The problem is not bad plans. The problem is that discovery and planning happen in the same step.

You sit down, think about what to build, write phases, estimate time, and start coding. But you have not checked whether someone already solved 80% of this. You have not verified that the API you are counting on actually supports what you need. You have not asked whether there is a fundamentally different approach.

The insight was simple: separate discovery from planning completely. Run discovery first, then plan based on what you actually know.

The Framework: 3 Stages

I formalized this into a framework that Claude Code runs automatically before every non-trivial project. After hundreds of handoffs and iterations, it stabilized into three stages.

Stage 0: Before the Plan

This is the most important stage. It runs 10 discovery checks before you write anything. Not all 10 every time - Claude decides which ones matter based on context.

Three checks run on every non-trivial project:

1. Existing Work Audit - What already exists? I have lost count of how many times Claude found that my codebase already had 70% of what I was about to build.
2. Feasibility Check - Is this even possible as described? Catches impossible scope before you invest hours.
3. The AHA Check - Is there a fundamentally better approach? This single check has saved me more time than everything else combined.

The AHA check is where the magic happens. You want a custom CMS? "Considered Strapi? 90% of what you need, 10% of the effort." You want 50 blog posts? "5 deep pillar posts plus derivatives might outperform 50 shallow ones." It forces you to challenge your first idea before committing.

Stage 1: The Actual Plan

Five core sections, always required. No exceptions.

Context and Why tells Claude the problem in 3 sentences. Not "improve X" but WHY improve X. Success Criteria defines what DONE looks like - including what FAILED looks like. If you cannot write a failure condition, your criteria are too vague. Assumptions lists what you are betting on being true, with a validation method and what happens if you are wrong. Phases break work into 3-4 hour chunks with binary gates: pass or fail, nothing in between. Verification splits into automated and manual - if neither exists, you are shipping blind.

Then 14 conditional sections activate based on domain. Software projects get rollback, risk, and dependencies. Multi-agent systems add delegation and security. Business projects add timeline and stakeholder communication. Claude detects the domain automatically.

Stage 2: The Meta Check

After writing the plan, four checks catch what the plan itself missed. Delegation strategy assigns the right model and agent to each phase. Research needs flags which phases need web research during execution. Review gates confirm where to stop and validate. And an anti-pattern scan catches the 12 most common planning failures.

12 Anti-Patterns That Kill Plans

I cataloged the patterns that kept destroying my plans. The three deadliest:

Vague Success - Words like "improve", "better", "enhance" without numbers. If you cannot measure it, you cannot verify it. Fix: add specific thresholds.

Skipping Stage 0 - The most expensive plans I ever wrote skipped discovery entirely. They looked complete but missed something fundamental. The framework now flags any plan that starts at Phase 1.

Zombie Projects - Plans with no failure conditions and no timeout. They never officially fail, they just drain time. Fix: define what FAILED looks like and when to kill it.

Results After 6 Months

Before the framework: roughly 40% of my plans needed significant replanning mid-execution. After: that dropped to under 10%. The plans that do need changes hit a built-in replanning trigger instead of a crisis.

The biggest shift was not the plan quality - it was the discovery phase. Stage 0 kills bad ideas early. It finds existing solutions before you reinvent them. It forces you to challenge your first approach. The 30 minutes you spend on discovery saves hours of execution on the wrong thing.

This integrates directly with my memory system for tracking progress across sessions, my CLAUDE.md patterns for project-specific rules, and my hook automations for enforcing quality gates automatically.

It is Open-Source Now

I extracted the framework from my system and published it as a standalone Claude Code package on GitHub. Drop it into any project and Claude runs it automatically for every non-trivial plan.

Install in 30 seconds:

git clone https://github.com/PrimeLineDirekt/universal-planning-framework
cp -r universal-planning-framework/.claude/* your-project/.claude/

This gives you the planning rule, three slash commands (/plan-new, /interview-plan, /plan-review), and a planner agent. Works with any project type - software, content, business, infrastructure.

The framework is domain-agnostic. I use it for feature development, blog content calendars, context management, system migrations, and security audits. The conditional sections adapt automatically.

The full course covers how this framework integrates with memory, delegation, and hooks into a complete autonomous development system. The framework itself is free forever.