story-readiness

Validate story files for GDD, ADR, TR ID, and manifest version gaps.

Updated Apr 25, 2026
One-click install
npx skills add https://github.com/packetalien/cursor-game-studios --skill story-readiness-packetalien
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-readiness
Source: https://github.com/packetalien/cursor-game-studios/tree/main/.cursor/skills/story-readiness
Command: npx skills add https://github.com/packetalien/cursor-game-studios --skill story-readiness-packetalien

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill validates that a story file contains everything a developer needs to begin implementation—no mid-sprint design interruptions, no guessing, and no ambiguous acceptance criteria. It reports a per-story verdict of READY, NEEDS WORK, or BLOCKED with a clear gap description for non-ready stories.

Core Features & Use Cases

  • Load and cache reference documents (design/gdd, docs/architecture, ADRs, TR registry) to evaluate readiness consistently across stories.
  • Apply a phase-based readiness checklist (design completeness, ADR references, TR-ID validity, manifest version currency, engine notes, and manifest rules) to determine if a story is ready to implement.
  • Produce per-story verdicts and suggested remediation steps; supports sprint-level and epic-level scoping for planning.

Quick Start

Run the story-readiness check on a target story file to identify GDD, ADR, TR, and manifest gaps before starting work.

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 is ready for development before sprint planning?▼

Validate story readiness by checking GDD references, ADRs, TR-ID validity, and manifest versions against a deterministic checklist. The result is a per-story verdict of READY, NEEDS WORK, or BLOCKED with explicit gap descriptions to surface blockers before work begins.

What is story readiness validation and why do I need it?▼

Story readiness validation ensures a story file contains everything a developer needs to begin implementation without mid-sprint design interruptions. It verifies design completeness, ADR references, TR-ID validity, and manifest version currency to eliminate guessing and ambiguous criteria.

Can I validate readiness across an entire sprint or production epic?▼

Yes, story readiness checks apply to individual stories, entire sprints, or production epics. The skill evaluates each story against cached GDD, ADR, and TR registry references, then aggregates per-story verdicts to surface all blockers during planning.

How do I identify missing ADR and GDD references in my story files?▼

Run a story readiness check to identify missing ADR and GDD references. The skill loads and caches design and architecture documents, applies a phase-based checklist, and outputs explicit gap descriptions with suggested remediation steps for non-ready stories.

Does story readiness validation check manifest versions and engine notes?▼

Yes, the readiness checklist validates manifest version currency, engine notes, and manifest-rule notes alongside design completeness, ADR references, and TR-ID validity to determine if a story is fully prepared for implementation.

What should I do when a story gets a BLOCKED readiness verdict?▼

A BLOCKED verdict includes explicit gap descriptions and suggested remediation steps. Resolve the identified GDD, ADR, TR-ID, or manifest version gaps in the story file before re-running the readiness check to achieve a READY status.