Agent skill · affaan-m
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.
What it needs
About 11k tokens when loaded.
What this skill does
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 When NOT to Use 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 Authority .stories/ is an opt-in planning projection. It is never canonical ECC Task, Evidence, Completion, or Integration state. Where ECC execution-capsule contracts, an issue tracker, or another external task/evidence system is configured, that system stays authoritative: the ledger only mirrors outcomes that system has already recorded, and it never asserts completion or integration on its own. .stories/ follows the checkout. Another branch shows that branch's ledger, and stories created on an unmerged branch are not visible elsewhere until that branch is merged. Boundary with GitHub-backed coordination ECC's epic- commands own issue-backed coordination: GitHub issues are the authority, labels and issue bodies carry state, and multiple agents can claim work. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/story-lifecycle