story-readiness

Validate story files for GDD traceability, ADR alignment, and acceptance criteria.

Updated Mar 28, 2026
One-click install
npx skills add https://github.com/scomofo/dragon-forge --skill story-readiness-scomofo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-readiness
Source: https://github.com/scomofo/dragon-forge/tree/main/.agents/skills/story-readiness
Command: npx skills add https://github.com/scomofo/dragon-forge --skill story-readiness-scomofo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams confirm that an epic/story file is truly implementation-ready so developers don’t start work and then hit mid-sprint gaps like missing GDD traces, outdated architecture rules, unclear acceptance criteria, or absent evidence requirements.

Core Features & Use Cases

  • Story-readiness validation: Checks each story for required structure, testable acceptance criteria, and clear evidence expectations based on story type.
  • Architecture and traceability checks: Verifies referenced ADRs (and whether they are Accepted), optional TR-IDs, and control-manifest “Manifest Version” alignment when present.
  • Scope and dependency sanity: Ensures estimates exist, dependencies are declared, out-of-scope boundaries are unambiguous, and blocked/draft dependency stories are handled properly.
  • Asset reference existence checks: Detects referenced asset paths and verifies they exist (existence-only), flagging missing files as gaps.

Quick Start

Use the story-readiness skill to validate a single story file at production/epics/hatchery/story-005-dragon-unlock-duplicate-xp-and-shiny-upgrade.md and get a READY/NEEDS WORK/BLOCKED verdict with a 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 validate story readiness before development starts?▼

Check story readiness by enforcing deterministic checklist rules across GDD traceability, architecture alignment, testable acceptance criteria, and scope clarity to generate a structured READY, NEEDS WORK, or BLOCKED verdict with missing items and blockers.

What is story readiness validation in game project management?▼

Story readiness validation verifies that epic and story files contain required structure, declared dependencies, and evidence expectations, preventing developers from hitting mid-sprint gaps like missing GDD traces or outdated architecture rules.

Can I check all stories in a sprint for missing acceptance criteria?▼

You can validate a single story file, all stories in a sprint, or all production epic stories to ensure testable acceptance criteria, evidence requirements, and dependency declarations exist before coding begins.

How do ADR validation and GDD traceability checks work together?▼

ADR validation confirms referenced Architecture Decision Records are Accepted, while GDD traceability checks ensure story requirements map back to the Game Design Document, together resolving review-mode behavior and flagging missing items as gaps.

What happens when dependency checks find blocked or draft stories?▼

Dependency checks flag blocked or draft dependency stories as gaps, ensuring estimates exist, out-of-scope boundaries are unambiguous, and referenced asset paths are verified for existence to prevent mid-sprint blockers.

Does story readiness validation verify asset reference paths?▼

Asset reference existence checks detect referenced asset paths and verify they exist on the file system, flagging any missing files as gaps within the structured readiness verdict.