story-done

Verify acceptance criteria, design compliance, and test coverage for game development sprint stories.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/CarlosQ96/robot-crawler --skill story-done
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/CarlosQ96/robot-crawler/tree/main/.agents/skills/story-done
Command: npx skills add https://github.com/CarlosQ96/robot-crawler --skill story-done

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Story completion in game development often lacks systematic verification, leading to missed acceptance criteria, undocumented design deviations, and delayed sprint flow. This Skill automates the end‑of‑story review, ensuring all checks are performed before marking a story complete and automatically surfaces the next ready story.

Core Features & Use Cases

  • Acceptance Criteria Verification: Automatically checks file existence, test results, and performs manual confirmations where needed.
  • Design Deviation Detection: Compares implementation against current GDD requirements, manifest versions, and ADR constraints.
  • Test‑Criterion Traceability: Generates a coverage table and flags untested criteria.
  • Story Status Update & Next‑Story Surfacing: Updates the story status to Complete and suggests the next story in the sprint.

Quick Start

Ask the assistant to run the story‑done skill on the current sprint story.

Frequently Asked Questions about story-done

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

FAQPage Schema
How do I verify story completion for game development sprints?

Story completion is verified by automatically checking acceptance criteria, validating test coverage, and detecting design deviations against current GDD requirements before updating the sprint story status.

What is test-criterion traceability and how does it flag untested acceptance criteria?

Test-criterion traceability generates a coverage table mapping acceptance criteria to test results, automatically flagging any untested criteria to ensure systematic end-of-story review before sprint flow continues.

How do I check design compliance against GDD requirements during story review?

Design compliance is checked by comparing the implementation against current Game Design Document requirements, manifest versions, and ADR constraints to surface undocumented design deviations during story completion.

Can I automate sprint flow by surfacing the next ready story after completion?

Sprint flow is automated by updating the completed story status and immediately identifying and surfacing the next ready story in the sprint backlog, preventing delayed sprint transitions.

Does story completion verification require manual confirmations for acceptance criteria?

Acceptance criteria verification combines automated checks for file existence and test results with manual confirmations where needed, ensuring comprehensive coverage for game development sprint stories.

What's the best way to handle end-of-story review without missing acceptance criteria?

End-of-story review is handled by systematically verifying acceptance criteria, generating traceability reports, detecting design deviations from the GDD, and updating story status to complete before moving forward.