wbs-decomposition

Decompose team OKR targets into hierarchical WBS with milestones, workstreams, and tasks.

17|1|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/Adelie-Squad/solosquad --skill wbs-decomposition
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wbs-decomposition
Source: https://github.com/Adelie-Squad/solosquad/tree/main/skills/wbs-decomposition
Command: npx skills add https://github.com/Adelie-Squad/solosquad --skill wbs-decomposition

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PMs and teams struggle to translate high-level milestones (quarters, programs) into concrete, trackable work packages. This skill automates the translation into a structured WBS that can be scheduled and tracked.

Core Features & Use Cases

  • Milestone-to-WBS conversion: Breaks milestones into coherent workstreams and daily tasks with ownership.
  • Dependency graph & critical path: Automatically generates task dependencies and the critical path to guide prioritization.
  • Use Case: For quarterly planning, convert OKRs into Level 1 milestones, Level 2 workstreams, and Level 3 tasks with owners and target dates, ready for sprint planning.

Quick Start

Create an input that includes team OKRs and a proposed milestone, then run wbs-decomposition to receive a structured plan ready for review.

Frequently Asked Questions about wbs-decomposition

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

FAQPage Schema
How do I decompose team OKRs into a hierarchical WBS for quarterly planning?

To decompose team OKRs into a hierarchical WBS, you provide the OKRs and proposed milestones to generate Level 1 milestones, Level 2 workstreams, and Level 3 tasks with owners and target dates ready for sprint planning.

What is the best way to generate a dependency graph and critical path from project milestones?

Generating a dependency graph and critical path from milestones requires breaking down milestones into trackable work packages, which automatically produces task dependencies and identifies the critical path to guide execution prioritization.

How does milestone-to-WBS conversion handle sprint-level planning?

Milestone-to-WBS conversion handles sprint-level planning by breaking coherent workstreams into daily tasks with clear ownership and target dates, satisfying structured outputs including total_estimate and open_questions for validation.

Can I use WBS decomposition for both quarterly programs and sprint-level execution?

Yes, you can apply WBS decomposition to both quarterly planning and sprint-level planning, translating high-level programs into concrete, trackable work packages complete with a dependency_graph and critical_path for execution.

What structured outputs should a milestone-to-WBS conversion produce?

Milestone-to-WBS conversion produces structured outputs including milestones, a dependency_graph, critical_path, total_estimate, and open_questions, providing clear validation and guardrails for the generated hierarchical tasks.

When do I need to convert high-level milestones into a work breakdown structure?

You need to convert high-level milestones into a work breakdown structure when PMs and teams struggle to translate quarters or programs into concrete, trackable work packages that can be scheduled and tracked.