Create Plans
Create hierarchical project plans optimized for solo agentic development.
Install
npx skills add glittercowboy/taches-cc-resources --skill create-plans -g -a claude-code -y- Repository
- glittercowboy/taches-cc-resources2k
- Category
- AI and agents
- Updated
- 7mo ago
- License
- MIT
- Context cost
- Mediumabout 3,000 tokens
- Runs scripts
- No, instructions only
What it does
Create hierarchical project plans optimized for solo agentic development. Use when planning projects, phases, or tasks that Claude will execute. Produces Claude-executable plans with verification criteria, not enterprise documentation. Handles briefs, roadmaps, phase plans, and context handoffs.
<essential_principles>
<principle name="solo_developer_plus_claude"> You are planning for ONE person (the user) and ONE implementer (Claude). No teams. No stakeholders. No ceremonies. No coordination overhead. The user is the visionary/product owner. Claude is the builder. </principle> <principle name="plans_are_prompts"> PLAN.md is not a document that gets transformed into a prompt. PLAN.md IS the prompt. It contains: - Objective (what and why) - Context (@file references) - Tasks (type, files, action, verify, done, checkpoints) - Verification (overall checks) - Success criteria (measurable) - Output (SUMMARY.md specification)When planning a phase, you are writing the prompt that will execute it. </principle>
<principle name="scope_control"> Plans must complete within ~50% of context usage to maintain consistent quality.The quality degradation curve:
- 0-30% context: Peak quality (comprehensive, thorough, no anxiety)
- 30-50% context: Good quality (engaged, manageable pressure)
- 50-70% context: Degrading quality (efficiency mode, compression)
- 70%+ context: Poor quality (self-lobotomization, rushed work)
Critical insight: Claude doesn't degrade at 80% - it degrades at ~40-50% when it sees context mounting and enters "completion mode." By 80%, quality has already crashed.
Solution: Aggressive atomicity - split phases into many small, focused plans.
Examples:
01-01-PLAN.md- Phase 1, Plan 1 (2-3 tasks: database schema only)01-02-PLAN.md- Phase 1, Plan 2 (2-3 tasks: database client setup)01-03-PLAN.md- Phase 1, Plan 3 (2-3 tasks: API routes)01-04-PLAN.md- Phase 1, Plan 4 (2-3 tasks: UI components)
Each plan is independently executable, verifiable, and scoped to 2-3 tasks maximum.
Atomic task principle: Better to have 10 small, high-quality plans than 3 large, degraded plans. Each commit should be surgical, focused, and maintainable.
