wbs

Decompose project scope into hierarchical work packages with WBS dictionary generation.

Updated Nov 21, 2025
One-click install
npx skills add https://github.com/HaRu-LLC/ai-pm_system_notebooklmuse --skill wbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wbs
Source: https://github.com/HaRu-LLC/ai-pm_system_notebooklmuse/tree/main/.agent/skills/pm/planning/wbs
Command: npx skills add https://github.com/HaRu-LLC/ai-pm_system_notebooklmuse --skill wbs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Breaks down a project's scope into manageable work packages, enabling clear planning, tracking, and delivery control.

Core Features & Use Cases

  • Hierarchical decomposition: splits scope from major deliverables down to activities, creating a level-based WBS.
  • WBS dictionary generation: automatically documents descriptions for each work package for scope clarity.
  • Output & governance: saves the WBS to a standardized location and supports alignment with PMBOK principles.

Quick Start

Provide your project name and major deliverables, and indicate the desired decomposition depth to generate the WBS.

Frequently Asked Questions about wbs

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

FAQPage Schema
How do I break down project scope into manageable work packages for tracking?

To break down project scope into work packages, you decompose major deliverables hierarchically down to activities. This creates a level-based work breakdown structure that enables clear planning, tracking, and delivery control.

What is a WBS dictionary and how does it help with scope management?

A WBS dictionary documents descriptions for each work package to ensure scope clarity. It defines specific deliverables and activities within the work breakdown structure, supporting PMBOK-based planning principles and governance.

How do I create a work breakdown structure aligned with PMBOK planning principles?

You create a PMBOK-aligned work breakdown structure by providing your project name and major deliverables, then indicating the desired decomposition depth. This guides scope breakdown from major deliverables down to activities.

Can I apply work breakdown structure techniques to small projects across different industries?

Yes, work breakdown structure techniques apply to projects of varying size across industries. Decomposing scope into work packages supports planning, tracking, and control regardless of the specific industry context.

What level of decomposition depth should I use for task decomposition in project management?

Decomposition depth for task decomposition depends on your project's complexity and tracking needs. You indicate the desired depth to split scope from major deliverables down to activities, creating a level-based WBS.

Does generating a work breakdown structure require specific project management software dependencies?

No specific project management software dependencies are required. You provide the project name and major deliverables to generate the WBS, which is saved to a standardized location for output and governance.