story-lifecycle
Manage a file-based epic → story → sprint development loop without requiring an external project management tool. Creates and tracks epics, breaks them into user stories, assigns them to sprints, and drives implementation story by story. Use when starting a new feature initiative or when the team has no Jira/Linear/Taiga but needs structured delivery tracking.
Target: Target not categorized. Automatically collected · unverified.
Excerpt from the author’s documentation
Extracted from a fixed version of SKILL.md in its original language. This is the author’s documentation; installation, compatibility and runtime results have not been verified by this site.
Read the original English text
Topics in the source
- 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
This is an excerpt. Refer to the complete source and its current requirements.
- Source repository
- affaan-m/ECC
- Source file
- skills/story-lifecycle/SKILL.md
- Fixed revision
- d2ef2680594f9a17526a6e1a2e18b3d242c5d17b
Sources and evidence
This record was collected automatically. Its documentation, suitability and runtime behavior have not been manually verified.
Author: affaan-m/ECC · original repository metadata. Documentation review: Not reviewed. Last source check: 2026-11-09T16:01:00.577Z.
Categories are inferred from names, descriptions and paths. They do not establish compatibility.
License and attribution
MIT. Third-party content and copyright remain with their authors. Refer to the original license and terms.
Original license ↗Synchronization, copying and user-reported success do not mark a resource as runtime-tested.
Limitations and notes
- Collecting metadata does not mean this site has installed, adapted, runtime-tested or security-reviewed the resource.