Handbook
WBS — Work Breakdown Structure
Hierarchical decomposition Theme → Epic → Story → Task; Task maps to Forge Spark when IDs align.
What it is
Template at blueprints/pdlc/templates/WBS.template.md. IDs like M1E1S1T1 shared with planning.
When people say this
When breaking down Product Sparks, roadmaps, or aligning milestones M1… with delivery tasks.
Where it lives
blueprints/pdlc/templates/WBS.template.md
How it fits the ecosystem
Forge Spark = WBS Task — one ID spine, not duplicate hierarchies (per NAMING-REFERENCE).
Typical usage in plans and chat
Roadmap DoR should precede WBS expansion in Forge Product Manager flows.
Related terms
Term page — canonical catalog entry wbs.