New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Story Lifecycle

by Inebrio in Inebrio/Routerly

Run one user story end to end in its own worktree, from claim to merge.

AGPL-3.0Auto-check passedProduct & Project Management

Install Story Lifecycle

skills CLI
$ npx skills add Inebrio/Routerly --skill story-lifecycle -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Inebrio/Routerly story-lifecycle --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Inebrio/Routerly.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/story-lifecycle .claude/skills/story-lifecycle && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
story-lifecycle
GitHub stars
101
Token cost
~905 tokens
SKILL.md length
508 words
Files
1
Skills in repo
17
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Run one user story end to end in its own worktree, from claim to merge.

  • Works in 7 steps: Claim → Read → Freeze the interface → …
  • You are responsible for delivering a single story
  • SKILL.md covers 1. Claim, 2. Read, 3. Freeze the interface and 4. Implement, plus 5 more sections
  • Calls node

What it does

Story Lifecycle is an agent skill from Inebrio/Routerly. Run one user story end to end in its own worktree, from claim to merge. Use when you are responsible for delivering a single story.

Its SKILL.md is about 910 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Product & Project Management, covering Git worktrees and User stories. The repository describes itself as: Self-hosted LLM gateway that routes requests across AI providers (OpenAI, Anthropic, Gemini, Mistral, Ollama) using intelligent multi-policy scoring — including an LLM-native… The licence is AGPL-3.0.

When your agent uses it

  • You are responsible for delivering a single story
  • Tasks that involve Git worktrees
  • Tasks that involve User stories

Example prompts

  • “/story-lifecycle”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Claim
  2. Read
  3. Freeze the interface
  4. Implement
  5. Validate
  6. Test and document
  7. Hand back

What it can do on your machine

Read from SKILL.md and the folder at commit bcf58f1. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Story Lifecycle loads about 905 tokens when it runs. Until then it costs about 37 tokens; SKILL.md has 508 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~37
When it runs · the whole SKILL.md, loaded when a task matches
~905

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Inebrio/Routerly at commit bcf58f1, republished under its AGPL-3.0 licence (© Inebrio). 508 words, ~905 tokens.

Download SKILL.mdSave it as .claude/skills/story-lifecycle/SKILL.md (or your agent's skills folder).
name
story-lifecycle
description
Run one user story end to end in its own worktree, from claim to merge. Use when you are responsible for delivering a single story.

Story lifecycle

One story, one worktree, one branch, one set of ports. You own it from claim to merge. Everything you need is in the artifacts: the story file and the blueprint. Nothing is handed to you in conversation.

1. Claim

node .Codex/scripts/story.mjs claim <story-id> --feature <feature> --base <integration-branch>

Returns the worktree path, the branch, the assigned ports, the specs path and the start command, and marks the story in-progress in the shared registry so no other session takes it or its ports.

Then work only inside that worktree. Every command you run starts by sourcing its environment:

set -a; . ./.Codex-story.env; set +a

Skip that and you run against the developer's own state, not the story's.

2. Read

The story file, then the blueprint, then the code the blueprint names. In that order. If the blueprint has a gap, it goes back to whoever wrote it: do not fill it yourself.

3. Freeze the interface

Before any code, every contact point between backend and frontend work is fixed and written down. See interface-contracts. Parallel work on an unfrozen interface is the one failure mode that costs a full rewrite.

4. Implement

Dispatch the blueprint's tasks: backend work to the backend engineer, interface work to the frontend engineer, in parallel when the blueprint says they are independent, sequentially when it does not.

Both work in this worktree. Neither invents a contract. When they disagree, you arbitrate; when the disagreement is about the plan or the story, it goes up.

5. Validate

Mark the story validating, then hand the validator the story, the blueprint and the diff. It runs the app on this worktree's ports and verifies every criterion against reality. It cannot change code, by design.

  • PASS, no blockers → continue.
  • BLOCKED → run remediation-loop. Three iterations, then escalate.
Show full SKILL.md (225 more words)Show less

6. Test and document

Only on validated code with zero blockers, and both at once: they read the same shipped code and neither blocks the other.

  • qa-engineer: one test per acceptance criterion, one regression test per blocking finding that was raised. Writes tests, never source.
  • docs-writer: every surface the change ships on, written against the code rather than the blueprint. Writes documentation, never source.

7. Hand back

Report: the branch, what shipped, the validation verdict with its evidence, the tests added, the non-blocking findings, and anything left unverified.

Integration is not yours. The session that owns the feature merges the story branch into the integration branch, in dependency order, and only then:

node .Codex/scripts/story.mjs state <story-id> done
node .Codex/scripts/story.mjs release <story-id>

release refuses to discard a worktree that still holds unmerged work. That refusal is a correct answer: merge first.

States

planned → in-progress → validating → done, with blocked as the exit when the loop caps out. Move the state as it changes, not at the end: the registry is how a parallel session knows what is happening.

Rules

  • Never touch a file outside your worktree. The specs directory is a symlink into the main checkout and is shared: write only your own story's artifacts there.
  • Never take a port that is not yours. They are assigned for a reason.
  • A story is done when the criteria pass with evidence, not when the code looks right.

© Inebrio, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/story-lifecycle of Inebrio/Routerly.

Open the folder on GitHubat commit bcf58f1

Compare with similar skills

Story Lifecycle next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Story Lifecycle compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Story Lifecycle this skillInebrio/Routerly101—~905Automated safety check: PassAGPL-3.0
Bmad Handoffaj-geddes/claude-code-bmad-skills488—~2kAutomated safety check: PassCustom licence
User Story Writerdeanpeters/Product-Manager-Skills7.2k2 repos~2.9kAutomated safety check: PassCustom licence
Ralph Tui Create Beadssubsy/ralph-tui2.5k1 repos~2.6kAutomated safety check: PassMIT
Agile Product Owneralirezarezvani/claude-skills28k3 repos~3.2kAutomated safety check: PassMIT
Ralph Tui Create Beads Rustsubsy/ralph-tui2.5k1 repos~2.8kAutomated safety check: PassMIT

Similar skills

  • Bmad Handoff

    aj-geddes/claude-code-bmad-skills

    Emits a dev-tool-agnostic handoff manifest from ready-for-dev stories so an external dev plugin or runner can pick up and execute the work.

    488 GitHub stars~2k tokensUpdated 3 mo ago
    Agent WorkflowsAuto-check passed

  • User Story Writer

    deanpeters/Product-Manager-Skills

    Writes user stories in Mike Cohn's format with Gherkin acceptance criteria, turning user needs into development-ready work with testable conditions.

    7.2k GitHub starsUsed in 2 repos~2.9k tokens
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create Beads

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution. An agent skill from subsy/ralph-tui.

    2.5k GitHub starsUsed in 1 repo~2.6k tokens
    Product & Project ManagementAuto-check passed

  • Agile Product Owner

    alirezarezvani/claude-skills

    Writes INVEST-checked user stories with acceptance criteria, splits epics, plans sprints from velocity and ranks the backlog with a weighted score.

    28k GitHub starsUsed in 3 repos~3.2k tokens
    Product & Project ManagementAuto-check passed

  • Ralph Tui Create Beads Rust

    subsy/ralph-tui

    Convert PRDs to beads for ralph-tui execution using beads-rust (br CLI).

    2.5k GitHub starsUsed in 1 repo~2.8k tokens
    Product & Project ManagementAuto-check passed

  • To Spec

    bestofjs/bestofjs

    Turn the current conversation into a spec and publish it to the project issue tracker — no interview, just synthesis of what you've already discussed.

    3.1k GitHub starsUsed in 21 repos~757 tokens
    Product & Project ManagementAuto-check passed

More from Inebrio/Routerly

All 17 skills in this repo

  • Docs Conventions

    Inebrio/Routerly

    Where documentation lives in this repository, how a page is structured, and what a change owes the docs.

    101 GitHub stars~624 tokensUpdated yesterday
    Auto-check passed

  • Feature Lifecycle

    Inebrio/Routerly

    Run a Tier 1 or Tier 2 feature end to end — feature level, story level, parallelism, integration, and retrospective.

    101 GitHub stars~3k tokensUpdated yesterday
    Auto-check passed

  • Test Conventions

    Inebrio/Routerly

    Where tests live in this repository, how to run them, and what a story owes in coverage.

    101 GitHub stars~467 tokensUpdated yesterday
    Auto-check passed

  • Validation Protocol

    Inebrio/Routerly

    How to validate a story against its criteria and write the report, including what counts as evidence and what counts as blocking.

    101 GitHub stars~628 tokensUpdated yesterday
    Auto-check passed

  • Analysis Format

    Inebrio/Routerly

    Shape of a feature analysis document (00-analysis.md). An agent skill from Inebrio/Routerly.

    101 GitHub stars~472 tokensUpdated yesterday
    Auto-check passed

  • Blueprint Format

    Inebrio/Routerly

    Shape of a story blueprint, the technical plan an orchestrator executes.

    101 GitHub stars~581 tokensUpdated yesterday
    Auto-check passed

Categories

Questions about Story Lifecycle

What does Story Lifecycle do?

Run one user story end to end in its own worktree, from claim to merge. Story Lifecycle is an agent skill from Inebrio/Routerly. Run one user story end to end in its own worktree, from claim to merge.

When should I use Story Lifecycle?

Story Lifecycle fits situations like: you are responsible for delivering a single story; tasks that involve Git worktrees; tasks that involve User stories.

How do I install Story Lifecycle in Claude Code?

Run `npx skills add Inebrio/Routerly --skill story-lifecycle -a claude-code`. Or copy the skill folder (.agents/skills/story-lifecycle in Inebrio/Routerly) into .claude/skills/story-lifecycle in your project. Claude Code loads it when a task matches its description.

How do I install Story Lifecycle in Codex?

Run `npx skills add Inebrio/Routerly --skill story-lifecycle -a codex`. Or copy the skill folder (.agents/skills/story-lifecycle in Inebrio/Routerly) into .agents/skills/story-lifecycle in your project. Codex loads it when a task matches its description.

Can I use Story Lifecycle in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Inebrio/Routerly --skill story-lifecycle -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/story-lifecycle, .gemini/skills/story-lifecycle, .github/skills/story-lifecycle and .opencode/skills/story-lifecycle in your project.

What does Story Lifecycle need to run?

Going by SKILL.md and its folder, Story Lifecycle needs the command-line tools its instructions call (node).

Does Story Lifecycle access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Story Lifecycle safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Story Lifecycle use?

Story Lifecycle is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Story Lifecycle use?

About 905 tokens (SKILL.md is roughly 3.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Story Lifecycle?

Skills that share tags, products or a category with Story Lifecycle: Bmad Handoff (aj-geddes/claude-code-bmad-skills, 488 stars), User Story Writer (deanpeters/Product-Manager-Skills, 7.2k stars), Ralph Tui Create Beads (subsy/ralph-tui, 2.5k stars) and Agile Product Owner (alirezarezvani/claude-skills, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Story Lifecycle?

Inebrio (a GitHub organization) maintains it in Inebrio/Routerly, which has 101 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 8, 2026.

Source: Inebrio/Routerly on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.