iteration-planning

Plan kanban and phased iterations using WIP limits, rolling commitment, and phase-gate semantics.

3|2|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/hero-engine/hero --skill iteration-planning-hero-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: iteration-planning
Source: https://github.com/hero-engine/hero/tree/main/domains/pm/skills/iteration-planning
Command: npx skills add https://github.com/hero-engine/hero --skill iteration-planning-hero-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams running kanban (continuous flow) or phased (discovery/design/build/launch) delivery presets have no sprint timebox or Shape Up cycle to plan against, so sprint-style velocity math and batch commitments produce broken planning artifacts. This Skill provides the correct planning model for those presets. ## Core Features & Use Cases - WIP Limit Reasoning: Set, interpret, and respond to work-in-progress limits as flow-diagnostic tools rather than walls, including what a breach signals and why raising the limit re-hides the problem. - Rolling Commitment Planning: Replace batch sprint commits with a pull policy where the team commits to finishing the top item of the ranked Story Queue one slot at a time. - Phase-Gate Semantics: Define explicit entry/exit criteria per phase, propose gate crossings via the Story phase field, and detect when gates have degraded into calendar deadlines. - Use Case: A kanban team with WIP limit 3 and one free slot asks what to plan next; the Skill directs pulling the top-ranked ready story, committing to finish it, and leaving the rest of the queue untouched. ## Quick Start Ask the planner to plan the next iteration for a kanban or phased preset team, naming the current WIP count and the ranked ready queue.

Frequently Asked Questions about iteration-planning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan iterations for a kanban team without sprints?▼

Kanban planning uses a pull policy instead of a batch commitment: when a work slot frees, pull the top-priority ready story and commit to finishing it. The plan is the pull policy plus the WIP limit, with cycle time per item replacing sprint velocity.

What is a WIP limit and how should I set one?▼

A WIP limit caps how many items can be in flight at a stage to expose flow problems. Start near the team's natural in-flight count, then tighten until the queue in front of the slowest stage becomes visible; too high is decorative, too low starves the team.

What should I do when a WIP limit is breached?▼

A breach signals that upstream work is arriving faster than the stage can finish. Respond by swarming to finish work or fixing the bottleneck, not by raising the limit, which re-hides the problem the breach revealed.

How is phased planning different from sprint planning?▼

Phased planning moves stories through discovery, design, build, and launch gates defined by explicit entry/exit criteria rather than dates. Planning asks which gate each story is at and what it needs to cross next, instead of sizing scope into a timebox.

When should I use sprint planning or Shape Up instead of this model?▼

Use sprint planning when work is genuinely time-boxed and estimated, and Shape Up cycle planning when work is shaped to an appetite and bet at a table. This model fits only continuous pull or gated phases where the question is what is ready to move next.