planning-strategy-guide

Automate complex task planning with six-phase analysis and dependency tracking.

9|1|Updated Nov 20, 2025

Search Tags:#planning #dependencies #decomposition #estimation #epic #risks #planning-strategy

Ready to run

npx skills add https://github.com/duongdev/ccpm --skill planning-strategy-guide

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: planning-strategy-guide
Source: https://github.com/duongdev/ccpm/tree/main/skills/planning-strategy-guide
Command: npx skills add https://github.com/duongdev/ccpm --skill planning-strategy-guide

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you plan complex tasks with phase-driven analysis, dependencies, risks, and effort estimation, and integrates with other CCPM planning aids.

Core Features & Use Cases

6 planning phases: Complexity, Scope, Dependencies, Risks, Task Breakdown, Effort Estimation.
Interactive planning: asks clarifying questions and routes to supporting skills (docs-seeker, sequential-thinking, etc.).
Linear integration: updates plans and generates implementation arguments for Linear.

Quick Start

Ask, "How should I plan this complex feature?" or run /ccpm:plan epic 'User authentication' to start planning.

Frequently Asked Questions about planning-strategy-guide

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

FAQPage Schema

How do I break down a complex feature into manageable tasks?▼

Feature decomposition uses phase-driven analysis to break down scope into dependencies, risks, and effort estimates. The planning-strategy guide applies six phases—complexity assessment, scope definition, dependency mapping, risk identification, task breakdown, and effort estimation—to systematically decompose large features into actionable work items.

What's the best way to estimate effort for an epic or complex project?▼

Effort estimation integrates complexity and scope analysis with dependency and risk assessment. By mapping task relationships, identifying blockers, and assessing risk impact, you get realistic effort projections that account for hidden complexity and upstream dependencies.

How do I identify dependencies and risks before starting development?▼

Dependency analysis and risk identification are core planning phases that map task relationships and potential blockers. The structured approach surfaces integration points, external dependencies, and risk factors early, enabling you to sequence work and plan mitigation before development begins.

Can I use this planning approach with Linear for tracking implementation?▼

Yes. The planning-strategy guide integrates with Linear, updating plans and generating implementation arguments that sync your structured breakdown directly into Linear tasks and epics for seamless tracking.

What questions should I ask when planning a complex task?▼

Start with clarifying questions about scope, complexity, and constraints. The planning guide routes you through six phases—asking about project scope, dependencies on other work, potential risks, task breakdown strategy, and effort required—then connects you to supporting skills like sequential thinking for deeper analysis.

When should I use phase-driven planning instead of ad-hoc task breakdown?▼

Use phase-driven planning for epics, features with cross-team dependencies, or tasks where scope uncertainty or risk could derail schedules. The structured six-phase approach prevents scope creep and hidden complexity from emerging mid-project.