Planning Skills
ido4 provides methodology-specific planning skills that compose execution containers following all governance constraints.
| Skill | Methodology | What It Plans |
|---|---|---|
/ido4dev:plan-wave | Hydro | Wave composition with epic integrity |
/ido4dev:plan-sprint | Scrum | Sprint planning with type-aware capacity |
/ido4dev:plan-cycle | Shape Up | Cycle betting with appetite constraints |
/ido4dev:plan-wave (Hydro)
Composes waves following all 5 Hydro governance principles.
What It Does
- Calls
get_standup_datafor current project state - Identifies tasks ready for wave assignment
- Groups tasks by epic (Epic Integrity)
- Analyzes dependency chains (Dependency Coherence)
- Estimates capacity using real throughput data from analytics
- Assesses risk levels and AI suitability distribution
- Validates the composed wave against all 5 principles
- Presents a valid-by-construction wave plan
Output
- Wave composition: which tasks go in which wave
- Epic groupings: showing integrity is maintained
- Dependency analysis: confirming all dependencies are satisfiable
- Capacity assessment: based on historical velocity
- Risk distribution: task risk levels and AI suitability breakdown
- Validation result: governance principle compliance
When to Use
- Beginning of a new wave
- After a wave completion/retrospective
- When re-planning due to scope changes
/ido4dev:plan-sprint (Scrum)
Sprint planning with type-aware capacity estimation.
What It Does
- Gathers project state and backlog
- Filters for Product Backlog items ready to pull into a sprint
- Checks DoR compliance per work item type (Stories need AC, Bugs need repro steps)
- Estimates sprint capacity using velocity data
- Respects dependency ordering
- Presents sprint backlog recommendation
Scrum-Specific Features
- Type-aware DoR check: Stories without acceptance criteria are flagged, not silently planned
- Velocity-based capacity: Uses real historical throughput, not story point estimates
- Sprint goal alignment: Prioritizes tasks that contribute to a cohesive sprint goal
- Spillover detection: Warns about unfinished work from previous sprint
/ido4dev:plan-cycle (Shape Up)
Cycle planning with appetite-driven betting table.
What It Does
- Gathers shaped pitches (tasks in Shaped status)
- Assesses appetite per bet (size: S/M/L/XL)
- Evaluates risk levels (flags rabbit holes)
- Checks cycle capacity against appetite budget
- Considers cooldown pipeline (what’s ready to bet on)
- Presents betting table recommendation
Shape Up-Specific Features
- Appetite check: Total appetite of bets must fit the cycle duration
- Circuit breaker awareness: Flags bets that were killed in previous cycles (potential re-bets)
- Scope variable: Recommends scope cuts when appetite is tight rather than extending time
- Cooldown pipeline: Shows what’s available in the cooldown for the next cycle