agentmods.dev

story-readiness

story-readiness is a skill for Claude Code from cenconq25/claude-code-app-studio. It costs 61 tokens per session (1,522 once invoked), scanned A, original, MIT.

A pre-development checklist that decides whether a user story contains enough information to implement safely. A user story is a small, defined piece of product work.

In plain words
What is it for?
Use it to review a story and receive a READY, NEEDS WORK, or BLOCKED verdict before implementation.
Why use it?
It exposes missing requirements, design details, architecture references, or unclear acceptance criteria before coding starts.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter.

not rated 40repo 4mo ago A scan 61 tokens original MIT

Good fit Use it to review a story and receive a READY, NEEDS WORK, or BLOCKED verdict before implementation.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/cenconq25/claude-code-app-studio/story-readiness
View source ↗ cenconq25/claude-code-app-studio
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add cenconq25/claude-code-app-studio --skill story-readiness
Clone the repo
git clone --depth 1 https://github.com/cenconq25/claude-code-app-studio

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for story-readiness

README.md
[![agentmods](https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/story-readiness/github.svg)](https://agentmods.dev/skills/cenconq25/claude-code-app-studio/story-readiness)
Your own site
<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/story-readiness"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/story-readiness/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for story-readiness

Your own site · 80×15
<a href="https://agentmods.dev/skills/cenconq25/claude-code-app-studio/story-readiness"><img src="https://agentmods.dev/badge/skills/cenconq25/claude-code-app-studio/story-readiness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,522 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.01522
Opus 5 $0.00030 $0.00761
Sonnet 5 $0.00012 $0.00304
Haiku 4.5 $0.00006 $0.00152

Measured 6d ago against content hash c6e9e8f9b716, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

story-readiness scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 6d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/story-readiness/SKILL.md · 192 lines

How it starts

The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Story Readiness

Fast pre-flight check on a story. Catches the gaps that would make /dev-story produce wrong code: missing TR-ID, Proposed ADR, missing UX spec for UI stories, ambiguous acceptance criteria.

Read-only. Outputs a verdict + checklist.

Purpose / When to Run

Run when:

  • A story has just been created and the engineer is about to start
  • A story sat in the backlog and might have stale references
  • The user types /story-readiness <path> or "is this story ready"

Inputs

  • Path to the story file (required)

Outputs

  • A printed verdict: READY, NEEDS WORK, or BLOCKED
  • A checklist showing each check's status

Phase 1: Resolve Path

If a slug is passed, glob production/epics/*/story-*-<slug>.md and find it. If multiple match, ask which.

If no argument, list stories with Status: Ready from production/epics/*/story-*.md and ask.

Phase 2: Read

  • The story file
  • The PRD it references (just enough to verify the TR-ID exists)
  • The governing ADR (verify Status)
  • The control manifest (verify Manifest Version is current)
  • The UX spec (UI stories only)

Phase 3: Run Checks

Each check yields PASS / WARN / FAIL.

3a: Header completeness

  • Status line present and one of Ready / In Progress / Blocked / Complete — FAIL otherwise
  • Type line present — FAIL if missing
  • Manifest Version line present — WARN if missing, FAIL if older than 30 days from today (probably stale)
  • Layer line present — WARN if missing

3b: Context section

  • PRD path resolves to an existing file — FAIL otherwise
  • TR-ID is referenced and is in the format TR-<system>-NNN — FAIL if malformed
  • TR-ID exists in tr-registry.yaml (if registry exists) or in the referenced PRD — WARN if not found
  • Governing ADR path resolves to an existing file — FAIL otherwise
  • Governing ADR has Status: Accepted — FAIL if Proposed (recommend Status: Blocked)
  • Framework risk recorded — WARN if missing
  • Verification required field has content (or explicit "None") — WARN if empty

Read the full file on GitHub · 192 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 6d ago First seen · 192 lines · 61 tokens per session scan A c6e9e8f9b716

Subscribe to this mod's changes

story-readiness is a skill published in the GitHub repository cenconq25/claude-code-app-studio (40 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 1,522 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

PlanningProject management
Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

story-readiness

Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…

Donchitos/Claude-Code-Game-Studios · 77 tokens

autotask-creator

Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.

Orkas-AI/Orkas · 5 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens