Agent skill · operations · aiskillstore
project-planner
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.
Why this skill is useful
Codifies project planning processes and task breakdown standards that the AI could infer but now doesn't have to guess.
What it needs
About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
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 [Task A] ──> [Task B] ──> [Task D] ├──> [Task C] ──┘ Estimation Techniques Three-Point Estimation T-Shirt Sizing XS: < 2 hours S: 2-4 hours M: 4-8 hours (1 day) L: 2-3 days XL: 1 week Break down anything larger than XL Planning Poker For team estimation, use Fibonacci: 1, 2, 3, 5, 8, 13 story points Example User Request: "Plan a website redesign. Team: 1 designer, 2 developers. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/project-planner--22be6e