Phase 1b: Rename all ~94 commands across 12 plugins to /<noun> <action> sub-command pattern. Git-flow consolidated from 8→5 commands (commit variants absorbed into --push/--merge/--sync flags). Dispatch files, name: frontmatter, and cross-reference updates for all plugins. Phase 2: Design documents for 8 new plugins in docs/designs/. Phase 3: Scaffold 8 new plugins — saas-api-platform, saas-db-migrate, saas-react-platform, saas-test-pilot, data-seed, ops-release-manager, ops-deploy-pipeline, debug-mcp. Each with plugin.json, commands, agents, skills, README, and claude-md-integration. Marketplace grows from 12→20. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
46 lines
1.3 KiB
Markdown
46 lines
1.3 KiB
Markdown
---
|
|
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
|
|
|
|
1. **Level 1:** Epics (from project charter)
|
|
2. **Level 2:** Work packages (groupings within an epic — typically 1 sprint each)
|
|
3. **Level 3:** Tasks (become Gitea issues — must be S or M size per task-sizing.md)
|
|
|
|
## Sprint Refinement
|
|
|
|
During `/sprint plan`, the planner:
|
|
1. Loads the WBS
|
|
2. Identifies the next unstarted work packages
|
|
3. Creates issues from Level 3 tasks
|
|
4. 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
|