Menu

Individual skill

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.

skills/story-lifecycle/SKILL.md

Read pinned source

Source commit b38be6a7f6350964d59328b52f0624e1d1d552d1

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 3, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
299,326
Repository last updated
Nov 6, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# 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](#authority) and
[Boundary with GitHub-backed coordination](#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"