create-plans

Translate project briefs into Claude-executable phase plans and summaries.

5|3|Updated Jan 6, 2026
One-click install
npx skills add https://github.com/durandom/skills --skill create-plans-durandom
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plans
Source: https://github.com/durandom/skills/tree/main/.claude/skills/create-plans
Command: npx skills add https://github.com/durandom/skills --skill create-plans-durandom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured approach to planning software projects with Claude by turning vision into executable, atomic PLAN.md prompts. It bridges BRIEF, ROADMAP, and phase artifacts, enabling a solo developer and Claude to plan, execute, and ship with strict context management and maintainable git history.

Core Features & Use Cases

  • Executable planning: Generates Claude-executable PLAN.md per phase with objective, context, tasks, verification, and success criteria.
  • Context-aware loading: Selectively loads domain knowledge and references to keep context usage efficient.
  • Progress capture & handoffs: Creates SUMMARY.md after tasks, supports context handoffs for paused work, and updates ROADMAP accordingly.
  • Domain integration patterns: Supports optional domain expertise that can be loaded and referenced during planning to tailor tasks to specific tech stacks.
  • Version & milestone readiness: Works with BRIEF/ROADMAP/MILESTONES to track shipped milestones and plan future work.

Quick Start

  1. Invoke this skill to begin planning a new project: Skill("create-plans").
  2. Provide a BRIEF and ROADMAP (or let the skill guide you to create them).
  3. Generate phase plans (01-01-PLAN.md, etc.) and iterate until phase completion, then create SUMMARY.md.

Frequently Asked Questions about create-plans

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I break down a software project roadmap into executable phase plans for Claude?

Executable phase plans are generated by loading your project BRIEF and ROADMAP, then translating them into 2-3 atomic PLAN.md files that stay within a 50% context budget for Claude to execute in a single pass.

What is the best way to manage context limits when planning complex coding tasks with an AI assistant?

Managing context limits during planning requires selectively loading domain knowledge and references to stay within a 50% context budget, ensuring the generated phase plans remain executable within a single context window pass.

How do I create verifiable task milestones and handoff summaries for paused development work?

Verifiable task milestones and handoffs are created by generating a SUMMARY.md after task completion, which captures progress and supports context handoffs for paused work while updating the project ROADMAP accordingly.

Do I need a BRIEF and ROADMAP file before generating atomic phase plans?

A BRIEF and ROADMAP file are required as inputs to generate atomic phase plans, though the skill can guide you through creating these initial project artifacts if they do not already exist in your repository.

Can I integrate domain-specific tech stack knowledge into my project's phase planning workflow?

Domain-specific tech stack knowledge can be optionally loaded and referenced during the planning workflow to tailor generated tasks, ensuring the phase plans align with your specific technical requirements and frameworks.

Why does context overflow happen when executing large project plans, and how can phase prompts prevent it?

Context overflow happens when plans exceed the model's window limits; phase prompts prevent this by structuring work into 2-3 atomic phases with strict context budgeting and selective loading of references.