project-breakdown

Break down project goals into milestones, tasks, estimates, and dependencies.

46|11|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/clawpod-app/awesome-openclaw-agent-packs --skill project-breakdown
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-breakdown
Source: https://github.com/clawpod-app/awesome-openclaw-agent-packs/tree/main/packs/project-planning/skills/project-breakdown
Command: npx skills add https://github.com/clawpod-app/awesome-openclaw-agent-packs --skill project-breakdown

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose vague goals into structured, actionable project plans with clear milestones, tasks, estimates, and dependencies.

Core Features & Use Cases

  • Milestone planning (3-6 milestones) with deliverables
  • Task breakdown (3-8 tasks per milestone) and ownership assignment
  • Estimate aggregation, dependency mapping, and critical-path identification
  • Generates a reusable project plan suitable for kickoff and progress reviews

Quick Start

Plan a project by providing a goal and constraints to generate a complete, actionable project plan.

Frequently Asked Questions about project-breakdown

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

FAQPage Schema
How do I break down a project goal into milestones and tasks?

Project planning with this approach requires your goals, constraints, and success criteria as input. It then maps dependencies and aggregates estimates to identify the critical path, producing a formal plan with deliverables and timelines.

What is the best way to map task dependencies and identify the critical path?

Dependency mapping and critical-path identification are built into the project breakdown process. By defining task estimates and ownership, the resulting plan highlights dependencies to ensure accurate execution roadmapping and progress reviews.

Can I use this for product development and execution roadmapping scenarios?

Product development and execution roadmapping benefit from this structured planning approach. By inputting your success criteria, you receive a formal project plan with deliverables, timelines, and ownership assignments for progress reviews.

Do I need to provide success criteria to generate a project plan?

Success criteria, along with goals and constraints, are required inputs to produce a formal project plan. Without them, the generated milestones, task estimates, and dependency mappings cannot accurately reflect the project deliverables.

How do I assign ownership and estimates when planning a project?

Assigning ownership and estimates is part of the task breakdown process, which creates 3-8 tasks per milestone. The plan then aggregates these estimates and maps dependencies to generate a reusable project plan for kickoffs.