skills.rest
frabcd
frabcdCOMMUNITY
Explore all skills by this author →
GitHub

story-readiness

Validates that game development story files are implementation-ready against a structured checklist.

13|Updated Jul 30, 2026
Search Tags:#game development#acceptance criteria#agile#sprint planning#story validation#readiness check#gdd
One-click install
npx skills add https://github.com/frabcd/codex-ai-game-studio --skill story-readiness-frabcd
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-readiness
Source: https://github.com/frabcd/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/story-readiness
Command: npx skills add https://github.com/frabcd/codex-ai-game-studio --skill story-readiness-frabcd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often assign stories that lack testable acceptance criteria, ADR references, or resolved design questions, causing mid-sprint interruptions and rework. This Skill audits story files before assignment and reports exactly what is missing. ## Core Features & Use Cases - Readiness Checklist: Evaluates design completeness, architecture references (GDD, ADR, TR-ID, control manifest), scope clarity, open questions, asset references, and definition of done per story. - Verdict Output: Assigns READY, NEEDS WORK, or BLOCKED per story with specific gaps and fixes, plus aggregate summaries for sprint or all-stories scopes. - Use Case: Before sprint planning, run the skill with the sprint scope to validate every story in the current sprint plan and receive a warning listing any Must Have stories that are not implementation-ready. ## Quick Start Ask the assistant to run story-readiness on a specific story file, the current sprint, or all stories under production/epics to get a readiness verdict with gaps.

Frequently Asked Questions about story-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if a user story is ready for implementation?▼

Run the story-readiness skill with the story file path as an argument. It evaluates design completeness, architecture references, scope clarity, and definition of done, then returns a READY, NEEDS WORK, or BLOCKED verdict with specific gaps.

How do I validate all stories in a sprint at once?▼

Pass the sprint scope argument to the skill. It reads the most recent sprint plan from production/sprints, extracts every referenced story path, validates each one, and warns if any Must Have stories are not implementation-ready.

What makes a story BLOCKED instead of NEEDS WORK?▼

A story is BLOCKED when a dependency story is missing or in DRAFT state, a referenced ADR is still Proposed or missing, or a critical design question is unresolved. NEEDS WORK applies to fixable gaps like missing estimates or untestable criteria.

Does the story readiness check modify story files?▼

No, the skill is strictly read-only. It reports findings and offers to draft missing sections in conversation, but the user or the create-stories skill handles all file writing.

What happens when a story references assets that do not exist?▼

The skill scans story text for asset paths such as images, audio, and scene files, then checks whether each file exists. Missing assets produce a NEEDS WORK verdict listing the missing paths, without validating file format or content.

Related Skills

Explore More Product & Management Skills→
kay6198835kay6198835

create-stories

Break epics into story files with TR-ID and ADR traceability.

Community
Advanced
DonchitosDonchitos
24.7k

story-done

Verifies story acceptance criteria, checks design deviations, and closes completed sprint stories.

Community
Advanced
nevesbnevesb

story-readiness

Validate story files for implementation readiness and produce READY, NEEDS WORK, or BLOCKED verdicts.

Community
Advanced
nevesbnevesb

quick-design

Draft lightweight design specs for small gameplay changes with acceptance criteria.

Community
Intermediate