Guides intelligent planning strategies with automatic phase detection and complexity assessment. Auto-activates when users mention epic breakdown, feature decomposition, scope estimation, dependency analysis, risk identification, or ask "how do I plan this complex task", "break down this feature", "what's the scope", "estimate effort", "identify dependencies", or "planning strategy". Provides interactive planning mode with 6 planning phases (complexity assessment, scope definition, dependency analysis, risk identification, task breakdown, effort estimation). Works with sequential-thinking for complex decomposition, docs-seeker for research, pm-workflow-guide for command suggestions, and linear-subagent-guide for Linear integration.
View on GitHubduongdev/ccpm
ccpm
January 24, 2026
Select agents to install to:
npx add-skill https://github.com/duongdev/ccpm/blob/main/skills/planning-strategy-guide/SKILL.md -a claude-code --skill planning-strategy-guideInstallation paths:
.claude/skills/planning-strategy-guide/# Planning Strategy Guide Expert planning assistant that helps you decompose complex tasks, assess complexity, identify dependencies, and create comprehensive implementation plans. ## When to Use This skill auto-activates when: - **Epic breakdown**: "Break down this epic into tasks" - **Feature decomposition**: "How do I plan this complex feature?" - **Scope estimation**: "What's the scope of this work?" - **Complexity assessment**: "How complex is this task?" - **Dependency analysis**: "What are the dependencies?" - **Risk identification**: "What risks should I consider?" - **Planning strategy**: "Help me structure this project" - **Effort estimation**: "I need to estimate effort for this" ## Planning Phases This skill guides you through **6 planning phases** for comprehensive task decomposition: ### Phase 1: Complexity Assessment **Purpose**: Evaluate task complexity to determine planning approach **Complexity Rubric**: - **Simple** (1-2 files, clear scope) - Single component modification - Well-defined requirements - No external dependencies - Estimated: 1-4 hours - **Medium** (3-8 files, some unknowns) - Multiple component changes - Some research needed - Few external dependencies - Estimated: 1-3 days - **Complex** (9+ files, research needed, multiple systems) - Cross-system changes - Significant research required - Many dependencies and integrations - Estimated: 4+ days **Questions to ask**: 1. How many files will be modified? 2. Are requirements fully understood? 3. Are there external system integrations? 4. How much research is needed? ### Phase 2: Scope Definition **Purpose**: Clearly define boundaries and deliverables **Key elements**: - **In scope**: What will be implemented - **Out of scope**: What will NOT be implemented - **Acceptance criteria**: How to verify completion - **Success metrics**: How to measure success **Questions to ask**: 1. What is the minimal viable implementation? 2. What features can be deferr