create-plans

Convert project ideas into Claude-executable planning artifacts under .planning.

2|1|Updated Nov 21, 2025
One-click install
npx skills add https://github.com/HelloWorldSungin/AI_agents --skill create-plans-helloworldsungin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-plans
Source: https://github.com/HelloWorldSungin/AI_agents/tree/main/.claude/skills/create-plans
Command: npx skills add https://github.com/HelloWorldSungin/AI_agents --skill create-plans-helloworldsungin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a principled, repeatable approach to converting project ideas into Claude-executable planning artifacts (BRIEF, ROADMAP, PLAN, SUMMARY). It ensures plans are deterministic, version-controlled, and ready for autonomous execution.

Core Features & Use Cases

  • Create Claude-executable planning artifacts (BRIEF.md, ROADMAP.md, PLAN.md, SUMMARY.md) with defined structure and frontmatter
  • Support hierarchical planning from brief to roadmap to phase plans, including context handoffs
  • Load domain expertise selectively and apply context-efficient references to keep token usage manageable

Quick Start

  • Run the create-plans skill to bootstrap a planning session from a BRIEF or to generate a roadmap from an existing brief.

Frequently Asked Questions about create-plans

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

FAQPage Schema
How do I turn project ideas into executable Claude plans for autonomous execution?

Creating executable Claude plans involves generating structured artifacts like BRIEF.md, ROADMAP.md, and PLAN.md that define context and tasks for deterministic, autonomous execution.

What is the best way to structure a Claude roadmap from an existing project brief?

The best way to structure a Claude roadmap from a brief is to use hierarchical planning that enforces a 2-3 task-per-plan discipline and manages context handoffs between phases.

How does domain-aware loading keep token usage manageable when generating execution plans?

Domain-aware loading keeps token usage manageable by selectively loading domain expertise references and applying context-efficient handoffs, ensuring only relevant context is processed during plan generation.

Can I integrate domain skills and handle deviations during automated plan execution?

Yes, you can integrate domain skills to improve planning quality and support deviations during execution, allowing the autonomous agent to adapt while maintaining version-controlled planning artifacts.

Do I need version control to manage hierarchical phase plans and summary files?

Version control is recommended for managing hierarchical phase plans and summary files, as the planning artifacts live under a .planning directory and are designed to be deterministic and version-controlled.