Template

Files

lmiranda 9ba2e660d3 feat(marketplace): hook migration, projman commands, optimizations [BREAKING]

Remove all SessionStart and PostToolUse hooks across the marketplace,
retaining only PreToolUse safety hooks and UserPromptSubmit quality hooks.
Add /project and /adr command families, /hygiene check, /cv status.
Create 7 new projman skills for project lifecycle management.
Remove /pm-debug, /suggest-version, /proposal-status commands.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

2026-02-06 12:28:06 -05:00

1.3 KiB

Raw Blame History

description

description
Work Breakdown Structure skill for decomposing projects and sprints into implementable work packages

Work Breakdown Structure (WBS)

Purpose

Bridges project-level epics and sprint-level issues. Used by /project plan to create the initial decomposition and by /sprint-plan to refine sprint scope.

Wiki Page

Page name: WBS: {Name} (e.g., WBS: Driving School SaaS)

Dependency Header

> **Project:** {Name}
> **Sprint:** N/A (project-level, refined per sprint)
> **Issues:** N/A
> **Parent:** Project: {Name}
> **Created:** YYYY-MM-DD
> **Status:** Draft | Active | Complete

Decomposition Rules

Level 1: Epics (from project charter)
Level 2: Work packages (groupings within an epic — typically 1 sprint each)
Level 3: Tasks (become Gitea issues — must be S or M size per task-sizing.md)

Sprint Refinement

During /sprint-plan, the planner:

Loads the WBS
Identifies the next unstarted work packages
Creates issues from Level 3 tasks
Marks consumed work packages as "Sprint-X" in the WBS

Integration

/project plan creates the initial WBS from epic decomposition
/sprint-plan consumes WBS work packages to create sprint issues
/sprint-close updates WBS with completion status
/project status aggregates WBS progress for project-level view

1.3 KiB Raw Blame History