apex-scope-wbs

Decompose project scope into a hierarchical WBS with dictionary and 100% rule validation.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill apex-scope-wbs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apex-scope-wbs
Source: https://github.com/JaviMontano/metodologia-propuesta-agent-public/tree/main/.claude/skills/governance/scope-wbs
Command: npx skills add https://github.com/JaviMontano/metodologia-propuesta-agent-public --skill apex-scope-wbs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The WBS Decomposition & Scope Management skill helps project teams create a complete, non-overlapping Work Breakdown Structure that covers 100% of the project's scope, producing a WBS tree and supporting dictionary artifacts to enable accurate planning and governance.

Core Features & Use Cases

  • Generate a hierarchical WBS with levels and PMI/ISO-21511 compliant codes
  • Create a WBS dictionary for each work package with description, acceptance criteria, owner, and estimates
  • Validate the 100% rule at every decomposition level to ensure full coverage and no overlaps
  • Define scope boundaries with explicit inclusions, exclusions, and gray zones
  • Support traceability from requirements and objectives to WBS, enabling RTMs
  • Suitable for Agile rolling-wave planning, waterfall baselining, and governance reviews

Quick Start

Provide the project charter and high-level scope; the skill will output a WBS tree, dictionary, and boundary definitions ready for scheduling.

Frequently Asked Questions about apex-scope-wbs

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

FAQPage Schema
How do I create a Work Breakdown Structure that satisfies the 100% rule?

To create a WBS satisfying the 100% rule, decompose your project scope into a hierarchical tree with non-overlapping deliverables, ensuring complete scope coverage at every level without gaps or overlaps.

What is a WBS dictionary and how does it support project governance?

A WBS dictionary is a supporting document defining each work package with descriptions, acceptance criteria, owners, and estimates. It enables project governance by providing traceability and clear scope boundaries for PMO workflows.

Can I use a WBS decomposition approach for Agile rolling-wave planning?

Yes, WBS decomposition supports Agile rolling-wave planning by progressively detailing scope boundaries. It adapts to Agile delivery models while maintaining traceability from requirements to work packages.

How do I define project scope boundaries to handle inclusions and gray zones?

Defining scope boundaries requires explicitly documenting inclusions, exclusions, and gray zones. This process establishes clear project limits, preventing scope creep and ensuring accurate WBS decomposition.

Does WBS traceability support Requirements Traceability Matrices for PMO workflows?

Yes, WBS traceability supports Requirements Traceability Matrices by mapping project objectives and requirements directly to WBS work packages, enabling validation and governance across traditional and Agile delivery models.

What inputs do I need to generate PMI compliant WBS codes and work packages?

Generating PMI compliant WBS codes requires a project charter and high-level scope definition as inputs. The decomposition process outputs a hierarchical WBS tree, dictionary artifacts, and explicit boundary definitions.