story-done

Validate game development story acceptance criteria, design compliance, and code review.

Updated Jul 22, 2025
One-click install
npx skills add https://github.com/MichaelSolati/mkai --skill story-done-michaelsolati
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/MichaelSolati/mkai/tree/main/profiles/game-dev/skills/story-done
Command: npx skills add https://github.com/MichaelSolati/mkai --skill story-done-michaelsolati

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game development teams often mark stories as complete without verifying all acceptance criteria, documenting design deviations, or ensuring code review is completed, leading to technical debt, missed requirements, and lost sprint momentum.

Core Features & Use Cases

  • End-to-End Story Validation: Automatically verifies every acceptance criterion against implementation, cross-checks GDD and ADR compliance, and enforces required test evidence based on story type.
  • Configurable Review Workflows: Supports solo, lean, and full review modes to adapt to different team sizes and sprint rigor, with optional QA coverage and lead programmer code review gates.
  • Sprint Momentum Maintenance: Automatically surfaces the next ready story from the sprint backlog and updates sprint status, reducing context switching and planning overhead. Use Case: A game dev team running 2-week sprints can use this skill to ensure every story is fully validated before closure, catch design drift early, and immediately start the next high-priority task without manual backlog triage.

Quick Start

Use the story-done skill to complete the review for your current in-progress game development story and get the next ready task to work on.

Frequently Asked Questions about story-done

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

FAQPage Schema
How do I validate agile story acceptance criteria before closing a game development sprint?

You can enforce test coverage traceability for game stories by requiring mandatory test evidence based on story type, ensuring every acceptance criterion links to verified tests before a story is marked as complete.

Can I use configurable code review workflows for different game development team sizes?

Configurable code review workflows support solo, lean, and full review modes to adapt to different team sizes. These modes offer optional QA coverage gates and lead programmer code review requirements based on sprint rigor.

How do I automatically surface the next ready story from my sprint backlog?

Automatically surfacing the next ready story from the sprint backlog happens when sprint status updates are applied after story validation. This reduces manual context switching and sprint planning overhead immediately after story closure.

What is the best way to log technical debt from design deviations during agile game development?

Logging technical debt from design deviations involves categorizing deviations from the Game Design Document during story validation. This captures design drift early and records tech debt systematically before closing the current sprint story.

Does this story validation process support different game development story types like logic, UI, and config data?

The story validation process supports logic, integration, visual and feel, UI, and config or data story types. Each type receives specific validation rules and test evidence requirements tailored to its technical scope.