skills.rest
claretagrapelike32
claretagrapelike32COMMUNITY
Explore all skills by this author →
GitHub

story-done

Verifies acceptance criteria, deviations, and test evidence before marking a story complete.

Updated Aug 2, 2026
Search Tags:#game development#code review#acceptance criteria#quality gate#story completion#sprint workflow#test traceability
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill story-done-claretagrapelike32
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/story-done
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill story-done-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Closing a development story often skips verification: acceptance criteria go unchecked, GDD/ADR deviations slip in silently, code review is forgotten, and story status files drift out of sync with reality. This Skill enforces a structured end-of-story review so nothing is marked done without evidence. ## Core Features & Use Cases - Acceptance Criteria Verification: Automatically checks file existence, test passes, and hardcoded values, and batches manual confirmations for subjective criteria. - Test-Criterion Traceability: Maps every acceptance criterion to a covering unit test, integration test, or manual confirmation, escalating to BLOCKING when coverage is insufficient. - Deviation and Evidence Gates: Compares implementation against the TR registry, GDD, ADRs, and manifest versions, and enforces test evidence requirements by story type (Logic, Integration, Visual/Feel, UI, Config/Data). - Use Case: After implementing a damage calculator story in a game project, run the review to verify all criteria pass, log advisory deviations to the tech debt register, update the story status to Complete, and surface the next ready sprint story. ## Quick Start Ask the assistant to run the story-done completion review on your current in-progress story file and report the verdict.

Frequently Asked Questions about story-done

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

FAQPage Schema
How do I verify acceptance criteria before marking a story complete?▼

Run the story-done review on the story file. It automatically checks file existence, test passes, and hardcoded values, then batches manual confirmation questions for subjective criteria like feel and gameplay behavior.

What is test-criterion traceability in a story review?▼

Traceability maps each acceptance criterion to a covering unit test, integration test, or confirmed manual playtest. If more than half of criteria are untested, the completion verdict is blocked until coverage improves.

Does the review enforce test evidence for different story types?▼

Yes. Logic stories require a passing unit test and Integration stories require an integration test or playtest record, both as blocking gates. Visual/Feel, UI, and Config/Data stories have advisory evidence requirements such as screenshots or smoke check reports.

What happens when implementation deviates from the GDD or ADR?▼

Deviations are categorized as BLOCKING when they contradict the GDD or ADR, ADVISORY when functionally equivalent, or OUT OF SCOPE when extra files were touched. Blocking deviations prevent a COMPLETE verdict until resolved.

Can I skip code review in lean or solo review modes?▼

In solo mode the code review gate is skipped entirely. In lean mode you confirm whether a separate code review was run, and the answer is recorded in the completion notes. Full mode spawns the lead-programmer review gate.

Why is my story completion verdict BLOCKED?▼

A BLOCKED verdict means acceptance criteria are failing, blocking deviations exist, or required test evidence is missing. The report lists exactly what must be fixed, and you can resolve items or explicitly override with documented risk.

Related Skills

Explore More Software Engineering Skills→
wsmanwsman
18

story-readiness

Validate implementation-ready stories and flag missing requirements before development begins.

Community
Advanced
imclabimclab
1

team-qa

Orchestrate a complete QA testing cycle for sprint or feature workflows.

Official
Advanced
johnatas-henriquejohnatas-henrique

story-done

Verify agile story completion against acceptance criteria and design documents.

Community
Advanced
FrancisVargaFrancisVarga

create-stories

Generates story files from epic GED requirements and ADR decisions with QA-ready acceptance criteria.

Community
Advanced