Same engine, different profiles → different tool counts. Methodology is data, engine is code.
States (7)
Backlog
In Refinement
Ready for Dev
In Progress
In Review
Done
Blocked
Transitions (9)
refine
ready
start
review
approve
complete
block
unblock
return
Containers (2)
Wave (execution)
Epic (grouping)
Pipelines
start → 6 steps
approve → 8 steps
block → 3 steps
Principles (5)
Epic Integrity
Wave Singularity
Dependency Coherence
Compliance
lifecycle: refine→ready→start→...→complete
Task Transition Tools
One tool per unique action from profile.transitions
refine_task
ready_task
start_task
review_task
approve_task
complete_task
block_task
unblock_task
return_task
Container Tools
Per container: list, get_status, assign, create, validate_completion
list_waves
get_wave_status
assign_task_to_wave
create_wave
validate_wave_completion
Resources + Prompts
Terminology adapts: "Wave" (Hydro), "Sprint" (Scrum), "Cycle" (Shape Up)
wave-status resource
analytics-wave resource
plan-wave prompt
retro prompt
BRE Validation Pipelines
Steps per action from profile.pipelines. Type-scoped overrides for Scrum.
start → SourceStatus + StatusTransition + ...
approve → PRReview + TestCoverage + ...
Transition tools
9 (refine, ready, start, ...)
8 (no refine)
10 (+ shape, bet, ship, kill)
Container tools
8 (wave + epic)
8 (sprint + epic)
11 (cycle + bet + scope)