story-done

Verify story implementation against acceptance criteria and design documents.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill story-done-polsegu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/polsegu/Claude-Code-Game-Dev/tree/main/.claude/skills/story-done
Command: npx skills add https://github.com/polsegu/Claude-Code-Game-Dev --skill story-done-polsegu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill removes uncertainty at the end of story implementation by verifying every acceptance criterion, checking for design and ADR deviations, prompting required reviews, and updating the story's completion status so work is not prematurely or incorrectly marked done.

Core Features & Use Cases

  • Acceptance Criteria Verification: Automatically checks file existence, runs referenced tests, and batches manual confirmations for subjective criteria.
  • Traceability & Evidence Mapping: Maps each acceptance criterion to its corresponding test or manual confirmation and produces a traceability table.
  • Gates & Reviews: Spawns QA and lead-programmer review gates in full-review mode, flags blocking or advisory deviations, and updates sprint/session state when approved.
  • Use Case: Ideal for developers and leads finishing a sprint task who need a repeatable, auditable process to confirm readiness and surface the next work item.

Quick Start

Run the story-done skill to verify the specified story file against acceptance criteria and design documents and then update the story status to Complete with completion 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 sprint story?

To verify acceptance criteria before closing a sprint story, map each criterion to corresponding tests or manual confirmations, check file existence, run referenced tests, and grep for hardcoded values to ensure full traceability and readiness.

What is story traceability and how does it map acceptance criteria to tests?

Story traceability maps each acceptance criterion to its corresponding test or manual confirmation, producing a traceability table that provides auditable evidence the implementation meets the specified requirements before status updates.

How do I check for design and ADR deviations during a code review?

To check for design and ADR deviations during a code review, read story files, GDD entries, and ADRs, then flag any blocking or advisory deviations found against the implementation to prevent incorrect completion.

Can I use story review gates for QA and lead programmer approvals?

Yes, you can spawn QA and lead-programmer review gates in full-review mode to prompt required reviews, flag blocking deviations, and update sprint or session state when the story is approved.

What is the best way to update story status to complete with auditable evidence?

The best way to update story status to complete is by verifying implementation against acceptance criteria, generating a traceability table, passing QA and code review gates, and then preparing completion notes for the status update.