wbs

Generates a Work Breakdown Structure decomposing project scope into deliverables and work packages.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill wbs-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: wbs
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/planning/wbs
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill wbs-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Project teams often move from a signed backlog and roadmap straight into development without a formal decomposition of scope, leaving work unassigned, dependencies invisible, and coverage gaps undetected. This Skill produces a signed, traceable Work Breakdown Structure that closes Phase 6 (Planning) and gates entry into Governance. ## Core Features & Use Cases - Hierarchical WBS generation: Decomposes project scope into phases, deliverables, and work packages following the 100% rule, mutual exclusivity, and the 8/80 sizing rule. - WBS dictionary: Produces detailed work package entries with owners, dependencies, acceptance criteria, and effort estimates. - Signature-gated validation: Enforces nine validation rules (signed prerequisites, canonical output path, no placeholders, correct document ID, approval authority row) before the Project Manager can sign off. - Use Case: After the backlog, roadmap, and Software Architecture Document are signed, run this Skill to produce documentation/06-planning/work-breakdown-structure.md plus a sources file, unlocking the governance-doc skill. ## Quick Start Ask the agent to generate the Work Breakdown Structure for the current project once the backlog, roadmap, and architecture documents are signed.

Frequently Asked Questions about wbs

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

FAQPage Schema
How do I create a Work Breakdown Structure from a product backlog?▼

Map each signed backlog user story to one or more work packages, group them under deliverables derived from the architecture components, and exclude Won't v1 items. This Skill automates that mapping and outputs a hierarchical WBS with a dictionary.

What documents are required before generating a WBS?▼

Three signed documents are required: the prioritized backlog, the execution roadmap, and the Software Architecture Document. The Skill blocks execution and reports which prerequisite is unsigned if any is missing.

What is the 8/80 rule in work breakdown structures?▼

The 8/80 rule sizes work packages between 8 and 80 hours of effort so they are assignable and trackable. The Skill applies this rule as a quality criterion and flags packages that are too large or too small.

Can the WBS be approved without a Project Manager signature?▼

No. The Project Manager is the designated Approval Authority and the approval table must list that role. Validation rule 7 blocks sign-off if the Project Manager row is missing from the document.

Why does WBS generation fail with a placeholder error?▼

Validation rule 3 rejects any document containing placeholder text patterns defined in project-config.md. Replace all bracketed template values with real project content before requesting a signature.