story-done

Close game-development story tasks by verifying acceptance criteria and design deviations.

72|7|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill story-done-striderza
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/story-done
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill story-done-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents stories from being marked complete without confirming that every acceptance criterion matches the implementation and that any design-document deviations are explicitly surfaced instead of silently introduced.

Core Features & Use Cases

  • Acceptance-criteria verification: Verifies each acceptance criterion via automated checks (file/test/string/value presence), guided manual confirmations, and flags unverifiable items for playtest.
  • Evidence and traceability: Builds a criterion-to-test traceability table, escalates when coverage is insufficient, and checks evidence requirements based on story type.
  • Design deviation detection: Flags GDD/ADR drift, manifest staleness, hardcoded value issues, and scope creep against the story’s stated boundaries.
  • Operational workflow closure: Updates the story status to Complete and recommends the next ready story in the sprint.

Quick Start

Run story-done production/sprints/<story-file>.md --review lean to verify the story’s acceptance criteria, detect deviations, and update the story to Complete with notes.

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 closing a game development story?

Detect design document deviations by performing GDD and ADR deviation checks, validating manifest staleness, identifying hardcoded value issues, and flagging scope creep against the story's stated boundaries during the review process.

How do I enforce test evidence requirements for sprint story completion?

Enforce test evidence by checking evidence requirements based on story type—Logic, Integration, Visual, UI, or Data—escalating when coverage is insufficient, and coordinating the QA and lead programmer gate approval before updating the story status.

Can I run a lean review to check story completion for simple logic tasks?

Yes, you can run a lean review by passing the lean argument to verify only the story's acceptance criteria and detect deviations without the full QA gate coordination, updating the story to Complete with notes if criteria pass.

What is the best way to prevent incomplete stories from being marked done in a sprint workflow?

Prevent incomplete stories from being marked done by enforcing a QA gate that surfaces design-document deviations explicitly, validates traceability coverage, and requires playtest confirmation for unverifiable acceptance criteria before status updates.

How do I update sprint workflow state after a story passes the QA gate?

Update sprint workflow state by changing the story status to Complete, recording review notes, and recommending the next ready story in the sprint based on the production review-state files and session state updates.