SKILL.md
Story Lifecycle
A self-contained, file-based delivery loop: Epic → Stories → Sprint → Implement → Done.
No external PM tool required. All ledger state lives in the repo under .stories/. This is
opt-in, project-local planning, not a synchronized project-management authority and
never canonical ECC execution state — see Authority and
Boundary with GitHub-backed coordination.
When to Activate
- Starting a feature initiative and wanting structured delivery without a Jira/Linear/Taiga setup
- Breaking down a PRD or architecture doc into implementable units
- User says "create epics and stories", "plan this sprint", "what's next to build", or "implement the next story"
- Onboarding a project that tracks work in markdown files