work-breakdown-structure

Decompose projects into deliverable-oriented WBS trees with dictionary entries.

1|Updated Nov 29, 2025
One-click install
npx skills add https://github.com/SSiertsema/claude-code-plugins --skill work-breakdown-structure
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: work-breakdown-structure
Source: https://github.com/SSiertsema/claude-code-plugins/tree/main/work-breakdown-structure/skills/work-breakdown-structure
Command: npx skills add https://github.com/SSiertsema/claude-code-plugins --skill work-breakdown-structure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Decompose a project into a deliverable-oriented work breakdown structure that respects the 100% rule and the 8/80 sizing guideline, ensuring all scope is captured and properly scoped.

Core Features & Use Cases

  • Deliverable-oriented hierarchy that prevents overlap and clarifies ownership.
  • WBS dictionary entries for each node, including description, acceptance criteria, and dependencies.
  • Milestones & dependencies mapping to WBS nodes to support release planning and tracking.
  • Diagram-ready structure suitable for tree views and visualizations.

Quick Start

Provide the project name, scope statement, and known deliverables to generate the WBS.

Frequently Asked Questions about work-breakdown-structure

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

FAQPage Schema
How do I create a work breakdown structure that captures all project scope?

A work breakdown structure dictionary provides detailed entries for each WBS node, including descriptions, acceptance criteria, and dependencies. It ensures clear scope definition and ownership verification for every deliverable in the project hierarchy.

What is the 8/80 sizing guideline in project management decomposition?

The 8/80 sizing guideline in project decomposition dictates that no work package should take less than 8 hours or more than 80 hours to complete. This rule ensures work breakdown structure nodes are properly scoped for accurate tracking and assignment.

How do I map milestones and dependencies within a WBS?

To map milestones and dependencies within a WBS, decompose your project into deliverable-oriented nodes and assign milestones to those nodes. This maps intra-WBS dependencies to support release planning and accurate project tracking.

What inputs do I need to generate a WBS tree and coverage matrix?

To generate a WBS tree and coverage matrix, you need a defined project name, a scope summary, and known deliverables. These inputs yield a structured WBS tree with dictionary entries, milestones, and a numbering scheme.