story-flywheellisted
Install: claude install-skill rterakedis/leanwheel-skills
# Story Flywheel Skill
**Goal:** Drive the epic to completion without manual story-by-story triggering. Automates create-story → dev-story → code-review in sequence, pausing only for human decisions and commit sign-off between stories.
**Iron rule:** Never start the next story until the user has committed and given explicit go-ahead.
**Branch files** — read each only when its trigger is reached, and re-read it then rather than relying on memory (a long epic compacts this context):
- Subagents unavailable (Activation step 4) → [inline-fallback.md](inline-fallback.md)
- User pre-authorizes auto-continue → [auto-pilot.md](auto-pilot.md)
- No story left in the epic (Phase 5) → [epic-boundary.md](epic-boundary.md)
---
## Activation
1. Determine which epic to run. Check in order:
- Explicit argument: `/story-flywheel {epic_num}` or `/story-flywheel {epic_num}-{story_num}`
- Active milestone with `in-progress` or `review` issues (resume in flight — see Resuming Mid-Epic)
- Lowest epic-numbered milestone that still has open issues (see epic discovery below)
- Ask: "Which epic should I run the flywheel on?"
**Epic discovery — sort by epic number in title, not by GitHub milestone ID.** Milestone IDs follow creation order; epics may be reordered or inserted later, so derive sequence from the number in the milestone title (e.g., `"Epic 3 — ..."` → epic 3).
```bash
# List all open milestones, extract epic number from title, sort by it, pick lowest
gh api rep