story-lifecycle

原文涵盖的主题

• Story Lifecycle
• When to Activate
• When NOT to Use
• Authority
• Boundary with GitHub-backed coordination
• Directory Layout
• Naming and path contract
• Writes go through the ledger helper

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. 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 | Condition | Use Instead | | --- | --- | | Work is coordinated through GitHub issues | the epic- commands (/epic-decompose, /epic-claim, /epic-sync, …) | | Team already uses Jira, Linear, or Taiga | project-flow-ops or the matching MCP integration | | One-off task with no breakdown needed | just do it | | Architecture design first | the architect agent, then return here | | PRD creation first | the /plan-prd command, then return here | .stories/ is an opt-in planning projection. It is never canonical ECC

这里只展示节选，请以完整原文和当前要求为准。