Help us improve
Share bugs, ideas, or general feedback.
From quorum
Decomposes project tracks into small implementable work packages sized for single agent sessions, traceable to PRD requirements. Outputs structured work-breakdown.md files.
npx claudepluginhub berrzebb/quorum --plugin quorumHow this agent operates — its isolation, permissions, and tool access model
Agent reference
quorum:agents/knowledge/references/planner/work-breakdownThe summary Claude sees when deciding whether to delegate to this agent
The work breakdown decomposes a track into **implementable work packages**. Each WB item is small enough for a single implementer agent session and traceable back to a PRD requirement. `{planning_dir}/{track-name}/work-breakdown.md` — one per track. ```markdown - Project-wide principles inherited from CLAUDE.md - Track-specific principles (e.g., "all new endpoints require FVM row") 1. `{TRACK}-...Expert C++ code reviewer that runs git diff, clang-tidy, and cppcheck on modified files. Focuses on memory safety, modern C++ idioms, concurrency, and performance.
Share bugs, ideas, or general feedback.
The work breakdown decomposes a track into implementable work packages. Each WB item is small enough for a single implementer agent session and traceable back to a PRD requirement.
{planning_dir}/{track-name}/work-breakdown.md — one per track.
# Work Breakdown: {Track Name}
## Working Principles
- Project-wide principles inherited from CLAUDE.md
- Track-specific principles (e.g., "all new endpoints require FVM row")
## Recommended Sequence
1. `{TRACK}-1` First work package
2. `{TRACK}-2` Second work package (requires {TRACK}-1)
3. `{TRACK}-3` Third work package (parallel with {TRACK}-2)
## {TRACK}-1 {Title}
- **Goal**: What this package achieves (1 sentence)
- **PRD**: FR-1 (links to the requirement this implements)
- **Prerequisite**: WB IDs or track names that must complete first
- **First touch files**:
- `src/path/to/file.ts` — description of change
- `src/path/to/other.ts` — description of change
- **Implementation**:
- Specific item 1
- Specific item 2
- **BE requirements**: (if FE task) What the BE must provide
- Endpoint: `POST /api/v1/resource`
- Response shape: `{ data: { id, name } }`
- **FE requirements**: (if BE task) What the FE will consume
- Component: `ResourceList` reads `GET /api/v1/resources`
- **Tests**:
- Unit: `tests/path/file.test.ts` — what to test
- Integration: `tests/path/integration.test.ts` — what to verify
- **Integration owner**: (for convergence points only) `true` — this WB is responsible for wiring all upstream producers into the runtime path. The implementer must verify that every dependency's public API is actually called, not just imported.
- **Done**:
- Verifiable exit condition (derived from FR acceptance criteria)
- If `integration_owner: true`: must also pass integration invariants (Runtime Entry Closure, Consumer Exists, Persistence Applied)
- Example: "`<test runner> tests/path/file.test.*` passes with 3+ test cases"
| Size | Files Changed | Tests Added | Typical Duration | Verdict |
|---|---|---|---|---|
| XS | 1-2 | 1-2 | < 15 min | OK, but consider merging with adjacent WB |
| S | 2-4 | 2-4 | 15-30 min | Ideal |
| M | 4-8 | 3-6 | 30-60 min | Acceptable |
| L | 8-15 | 5-10 | 60-90 min | Split if possible |
| XL | 15+ | 10+ | > 90 min | Must split |
dependency_graph to detect.