story-readiness

Validate story files for GDD requirements, ADR guidance, and acceptance criteria.

Updated Apr 4, 2026
One-click install
npx skills add https://github.com/WindXRan/y3td --skill story-readiness-windxran
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-readiness
Source: https://github.com/WindXRan/y3td/tree/main/.claude/skills/story-readiness
Command: npx skills add https://github.com/WindXRan/y3td --skill story-readiness-windxran

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents mid-sprint design interruptions by checking whether a story file includes all required GDD/ADR context, testable acceptance criteria, clear scope boundaries, and required evidence hooks so implementation can start immediately.

Core Features & Use Cases

  • Readiness verdicts for story files: Produces READY / NEEDS WORK / BLOCKED with a specific gap list for each non-ready story.
  • Flexible scope selection: Validates a single story path, the current sprint, all production epics, or sprint/epic-derived sets.
  • System and governance validation: Verifies GDD requirement references, ADR status (Accepted vs Proposed), TR-ID registry validity, manifest version currency, and required engine/control manifest notes.
  • Implementation readiness checks: Ensures estimates, in/out of scope boundaries, dependencies, no unresolved TBD markers, and a clear Definition of Done with minimum evidence per story type.
  • Asset reference existence checks: Detects referenced asset paths and confirms they exist (existence-only), flagging missing assets as NEEDS WORK.

Quick Start

Use the story-readiness skill to validate a specific story file at production/epics/your-epic/story-001.md.

Frequently Asked Questions about story-readiness

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

FAQPage Schema
How do I validate if a story file is ready for implementation?

Story readiness validation checks files for GDD requirements, ADR guidance, manifest rules, and testable acceptance criteria to produce READY, NEEDS WORK, or BLOCKED verdicts with precise gap lists.

What makes a user story blocked or need work before sprint planning?

A story gets a BLOCKED or NEEDS WORK verdict when it lacks accepted ADR status, unresolved TBD markers, missing estimates, unclear scope boundaries, or insufficient test evidence hooks, which prevents immediate implementation from starting.

How do I check acceptance criteria and test evidence for all stories in a sprint?

Sprint scope validation checks all current sprint stories for testable acceptance criteria, Definition of Done compliance, and minimum required evidence per story type to ensure implementation readiness.

Does story readiness validation check if referenced asset paths exist?

Yes, story readiness validation performs asset reference existence checks by detecting referenced asset paths and confirming they exist, flagging any missing assets with a NEEDS WORK verdict to prevent broken references during implementation.

What governance metadata is required for a story to be implementation-ready?

Implementation-ready stories require valid GDD requirement references, ADR status marked as Accepted rather than Proposed, valid TR-ID registry entries, and current manifest versions with required engine or control manifest notes.

Can I validate stories for a specific epic instead of the entire sprint?

Yes, you can validate a specific epic by selecting the epic-derived story set, which applies the same readiness and gating checks to all stories within that epic to unblock planning and implementation.