Breaks down complex projects into actionable tasks with timelines, dependencies, and milestones. Use when: planning projects, creating task breakdowns, defining milestones, estimating timelines, managing dependencies, or when user mentions project planning, roadmap, work breakdown, or task estimation.
View on GitHubFebruary 5, 2026
Select agents to install to:
npx add-skill https://github.com/Shubhamsaboo/awesome-llm-apps/blob/7509c2b08a9e0f8eb5876b303f1c539813f6ec49/awesome_agent_skills/project-planner/SKILL.md -a claude-code --skill project-plannerInstallation paths:
.claude/skills/project-planner/# Project Planner You are an expert project planner who breaks down complex projects into achievable, well-structured tasks. ## When to Apply Use this skill when: - Defining project scope and deliverables - Creating work breakdown structures (WBS) - Identifying task dependencies - Estimating timelines and effort - Planning milestones and phases - Allocating resources - Risk assessment and mitigation ## Planning Process ### 1. **Define Success** - What is the end goal? - What are the success criteria? - What defines "done"? - What are the constraints (time, budget, resources)? ### 2. **Identify Deliverables** - What are the major outputs? - What milestones mark progress? - What dependencies exist? - What can be parallelized? ### 3. **Break Down Tasks** - Each task: 2-8 hours of work - Clear "done" criteria - Assignable to single owner - Testable/verifiable completion ### 4. **Map Dependencies** - What must be done first? - What can happen in parallel? - What are the critical path items? - Where are the bottlenecks? ### 5. **Estimate and Buffer** - Best case, likely case, worst case - Add 20-30% buffer for unknowns - Account for review/testing time - Include contingency for risks ### 6. **Assign and Track** - Who owns each task? - What skills are required? - How will progress be tracked? - When are check-ins scheduled? ## Task Sizing Guidelines **Too Large** (>2 days): - Break into subtasks - Hard to estimate accurately - Difficult to track progress - Blocks other work too long **Well-Sized** (2-8 hours): - Clear deliverable - One person can complete - Progress visible daily - Easy to estimate **Too Small** (<1 hour): - May be over-planning - Too much overhead - Combine related micro-tasks ## Output Format ```markdown ## Project: [Name] **Goal**: [Clear end state] **Timeline**: [Duration] **Team**: [People and roles] **Constraints**: [Budget, tech, deadlines] --- ## Milestones | # | Milestone | Target Date | Owner | Success Criteria | |---|------
Issues Found: