story-readiness

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

39|6|Updated May 3, 2026
One-click install
npx skills add https://github.com/cenconq25/claude-code-app-studio --skill story-readiness-cenconq25
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-readiness
Source: https://github.com/cenconq25/claude-code-app-studio/tree/main/.claude/skills/story-readiness
Command: npx skills add https://github.com/cenconq25/claude-code-app-studio --skill story-readiness-cenconq25

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the pre-development gating of new stories by validating IDs, ADR references, and governance status to prevent misaligned work.

Core Features & Use Cases

  • Header completeness checks (Status, Type, Manifest Version, Layer)
  • Context verification (PRD path, TR-ID format, TR-ID registry, ADR status)
  • PRD/ADR references validation and UX/spec alignment
  • Governance and manifest pinning checks
  • Output of a deterministic verdict (READY / NEEDS WORK / BLOCKED) plus a structured checklist
  • Read-only validation to surface blockers early

Quick Start

Run /story-readiness <path-to-story>.md to obtain a verdict and a checklist.

Frequently Asked Questions about story-readiness

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

FAQPage Schema
How do I verify user story readiness before development begins?

To verify user story readiness, validate header completeness, TR-ID format, ADR references, and governance status to output a READY, NEEDS WORK, or BLOCKED verdict with a structured checklist.

What is pre-flight readiness verification for backlog stories?

Pre-flight readiness verification is an automated validation process that checks PRD paths, UX specs, acceptance criteria testability, and manifest pinning to prevent misaligned work before development starts.

How do I validate ADR references and TR-ID format in product workflows?

You validate ADR references and TR-ID format by verifying PRD/ADR existence and status against the TR-ID registry, ensuring all governance and context requirements are met before development.

Can I automate acceptance criteria testability checks for new stories?

Yes, you can automate acceptance criteria testability checks by running read-only validation on story files to surface blockers early and output a deterministic verdict with a structured readiness checklist.

What does a story readiness verdict of NEEDS WORK or BLOCKED mean?

A NEEDS WORK or BLOCKED verdict means the story failed pre-flight checks for header completeness, PRD/ADR references, TR-ID registry, or governance status, preventing development until the structured checklist issues are resolved.