wbs

Generate a structured Project+ WBS Excel file with hierarchical codes and owner mapping.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/kenmulford/PMSkills --skill wbs-kenmulford
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wbs
Source: https://github.com/kenmulford/PMSkills/tree/main/skills/wbs
Command: npx skills add https://github.com/kenmulford/PMSkills --skill wbs-kenmulford

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires openpyxl, and includes scripts (resource) components.

What problem does it solve?

This Skill helps PMs translate project descriptions into a structured, auditable Work Breakdown Structure (WBS) in Excel, enforcing Project+ conventions like the 100% rule and the 8–80 hour work package constraint.

Core Features & Use Cases

  • Draft-first WBS parsing: convert user input into a hierarchical set of codes, names, owners, and estimates.
  • Fidelity guardrails: enforce the 100% rule, limit work packages to 8–80 hours, and manage TBDs without fabricating data.
  • Multi-sheet output: generate a WBS sheet, a Work Package Summary, Draft Gaps, and an Integrity Issues sheet to support planning and governance.
  • Use Case: breakdown a project into deliverables and packages, then review gaps before scheduling and budgeting.

Quick Start

Provide a JSON payload describing your project with deliverables and estimates, then run the WBS script to render the .xlsx.

Frequently Asked Questions about wbs

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

FAQPage Schema
How do I generate a work breakdown structure in Excel from project data?

To generate a work breakdown structure in Excel, provide a JSON payload with deliverables and estimates to create a structured .xlsx file. The output includes hierarchical codes, owner mapping, and rollup totals.

What is the 100% rule in work breakdown structures and how is it enforced?

The 100% rule in work breakdown structures ensures all project scope is captured without missing work packages. It is enforced through fidelity guardrails that generate Draft Gaps and Integrity Issues sheets when scope gaps exist.

How do I enforce the 8-80 hour work package constraint for project scheduling?

Enforcing the 8-80 hour work package constraint limits task durations to a manageable range for project scheduling. The parsing logic applies this constraint automatically during draft-first WBS generation from input data.

Can I use openpyxl to create multi-sheet project management reports with rollup totals?

Yes, you can use openpyxl to create multi-sheet project management reports with rollup totals. The generated .xlsx output includes a WBS sheet, Work Package Summary, Draft Gaps, and an Integrity Issues sheet.

Does this work breakdown structure generator fabricate missing project estimates?

No, this work breakdown structure generator does not fabricate missing project estimates. Fidelity guardrails manage TBDs and highlight missing work packages by generating an Integrity Issues sheet rather than inventing data.

What is the best way to parse a large project description into hierarchical codes and owners?

The best way to parse a large project description into hierarchical codes and owners is using a draft-first WBS parsing approach. This handles projects of any size, mapping deliverables to structured codes before scheduling and budgeting.