skills.rest
easonlao
easonlaoCOMMUNITY
Explore all skills by this author →
GitHub

story-readiness

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

Updated Apr 25, 2026
Search Tags:#acceptance criteria#sprint planning#architecture governance#story readiness#ADR validation#GDD traceability#project QA
One-click install
npx skills add https://github.com/easonlao/jiazi-game --skill story-readiness-easonlao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-readiness
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/story-readiness
Command: npx skills add https://github.com/easonlao/jiazi-game --skill story-readiness-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents mid-sprint surprises by verifying a story file is complete enough for implementation, with testable acceptance criteria and required architectural/design references.

Core Features & Use Cases

  • Story completeness validation: Checks that the story references specific GDD requirements with traceable acceptance criteria that are testable and free of subjective/judgment-based language.
  • Architecture governance checks: Verifies referenced ADRs exist and are Accepted (or flags Proposed/missing ADRs), validates TR-IDs against the TR registry when available, and confirms control manifest rules and engine notes where applicable.
  • Delivery readiness gate: Ensures planning essentials like estimates, scope boundaries, dependencies, and a clear Definition of Done including sufficient testable criteria and test evidence requirements.

Quick Start

Run the story-readiness skill on a single story file path like production/epics/combat/story-001-basic-attack.md to receive a READY/NEEDS WORK/BLOCKED verdict with a concrete gap list.

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 story file is ready for implementation?▼

To check story readiness, validate the story file for GDD traceability, ADR references, and testable acceptance criteria. This process generates a structured READY, NEEDS WORK, or BLOCKED verdict with specific missing elements and blockers before assigning development work.

What is story readiness validation in sprint planning?▼

Story readiness validation is a pre-implementation check that verifies a story file has testable acceptance criteria, architectural governance references, and dependency resolution. It prevents mid-sprint surprises by ensuring planning essentials like estimates and scope boundaries are complete.

How do I validate acceptance criteria for subjective language before a sprint?▼

Validating acceptance criteria involves checking that story requirements are testable and free of subjective, judgment-based language. The validation process traces criteria back to specific GDD requirements and confirms a clear Definition of Done including test evidence requirements.

Can I batch validate multiple story files for an epic audit?▼

Yes, story readiness validation applies to sprint-based batches and full epic story audits. You can run validation across multiple story file paths to receive individual READY, NEEDS WORK, or BLOCKED verdicts with concrete gap lists for each story prior to implementation.

Does story readiness validation check ADR status and architecture governance?▼

Yes, architecture governance checks verify that referenced ADRs exist and are in an Accepted state. The validation flags Proposed or missing ADRs, validates TR-IDs against the TR registry, and confirms control manifest rules and engine notes where applicable.

Why does my story readiness validation return a BLOCKED verdict?▼

A BLOCKED verdict occurs when the story file has unresolved design questions or missing and DRAFT dependency stories. The validation output provides a specific gap list identifying these blockers, missing elements, and incomplete planning essentials preventing implementation.

Related Skills

Explore More Software Engineering Skills→
emcconnellemcconnell

create-stories

Break epics into traceable story markdown files with QA test cases.

Community
Advanced
jackmochjackmoch

Ticket Generation Skill

Generate implementation tickets with acceptance criteria and dependency mapping from design documents.

Community
Advanced
cenconq25cenconq25
39

story-readiness

Validate user story headers, TR-ID, ADR references, and governance status.

Community
Advanced
rakhnianskii9rakhnianskii9

test-evidence-review

Audit test evidence quality and story readiness across sprints.

Community
Advanced