skills.rest
dnkrow
dnkrowCOMMUNITY
Explore all skills by this author →
GitHub

story-done

Verify story acceptance criteria against GDD requirements and ADR decisions.

1|Updated May 15, 2026
Search Tags:#acceptance criteria#traceability#test evidence#story closure#adr compliance#gdd verification#code review gate
One-click install
npx skills add https://github.com/dnkrow/skill --skill story-done-dnkrow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/dnkrow/skill/tree/main/claude-global/story-done
Command: npx skills add https://github.com/dnkrow/skill --skill story-done-dnkrow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents design/implementation drift by checking that every acceptance criterion in a story is actually satisfied, that GDD/ADR deviations are explicitly surfaced, and that the story can be marked Complete only with sufficient evidence and review.

Core Features & Use Cases

  • Acceptance Criterion Verification: Confirms each requirement via file checks, tests, grep-based sanity checks, and targeted manual confirmations.
  • Spec Drift Detection: Cross-checks implementation against the latest TR registry (GDD rules), flags manifest staleness, and validates ADR constraints.
  • Gate-Oriented QA & Code Review: Triggers QA coverage and lead programmer review in full/appropriate modes, then produces a structured completion report and updates story status with notes.

Quick Start

Run the skill with: story-done production/sprints/your-sprint-story.md --review lean.

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 are met before closing a story?▼

To verify acceptance criteria before story closure, check tests, evidence, and traceability against referenced GDD requirements and ADR decisions. This confirms each requirement via file checks, tests, and targeted manual confirmations.

What is the best way to detect spec drift during story closure?▼

Detecting spec drift during story closure involves cross-checking implementation against the latest TR registry for GDD rules. This validates ADR constraints and flags manifest staleness to prevent design and frontend implementation drift.

How do I run a code review gate for completed frontend stories?▼

Running a code review gate for completed frontend stories triggers QA coverage and lead programmer review in appropriate modes. This produces a structured completion report and updates story status to mark it Complete reliably.

Does story closure require ADR compliance and GDD verification?▼

Story closure requires ADR compliance and GDD verification to prevent implementation drift. Deviations from GDD and ADR constraints must be explicitly surfaced, ensuring the story is marked Complete only with sufficient evidence and review.

Can I update story status and surface the next ready story after implementation?▼

You can update story status and surface the next ready story after running appropriate checks and QA code-review gates. This applies to end-of-implementation workflows for design projects where stories must be marked Complete reliably.

Related Skills

Explore More Software Engineering Skills→
emcconnellemcconnell

story-done

Verifies completed stories' acceptance criteria, design consistency, and prepares completion reports.

Community
Advanced
slgoodrichslgoodrich
121

user-story-templates

Generate user story templates with acceptance criteria and INVEST validation.

Community
Basic
WellApp-aiWellApp-ai
341

qa-planning

Generate numbered Gherkin scenarios and acceptance criteria for QA contracts.

Official
Advanced
patrickrmoorepatrickrmoore

sddp-checklist

Generate a structured quality checklist with acceptance criteria, non-functional requirements, and risks.

Community
Intermediate