skills.rest
johnatas-henrique
johnatas-henriqueCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

story-done

Verify agile story completion against acceptance criteria and design documents.

Updated Jul 16, 2026
Search Tags:#code-review#acceptance-criteria#agile-development#test-coverage#story-done#deviation-tracking#sprint-management
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill story-done-johnatas-henrique
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/story-done
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill story-done-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the risk of incomplete story closures, missed acceptance criteria, undocumented design deviations, and forgotten code reviews that create technical debt and derail sprint timelines.

Core Features & Use Cases

  • Automated Acceptance Criteria Verification: Checks each story criterion against implementation via file existence, test pass, and hardcoded value checks, with manual confirmation for subjective or gameplay-related criteria.
  • Design Document Alignment: Cross-references implementation against current GDD/ADR requirements to catch deviations, and enforces test evidence requirements based on story type (Logic, Integration, Visual/Feel, etc.).
  • Sprint Workflow Integration: Spawns QA lead and lead programmer review gates based on configured review mode, logs tech debt for advisory deviations, and surfaces the next ready story to maintain sprint momentum. Use Case: After implementing a damage calculator story for a 90s F1 racing game, run this skill to confirm all acceptance criteria pass, document any minor GDD deviations, and immediately get the next priority story to start.

Quick Start

Use the story-done skill to complete the active story in your current sprint 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 verify acceptance criteria before closing an agile story?▼

Verify acceptance criteria by checking file existence, running tests, and validating hardcoded values before story closure. Manual confirmation is required for subjective or gameplay-related criteria to ensure complete agile story verification.

How does design deviation tracking work during sprint story closure?▼

Design deviation tracking works by cross-referencing implementation against current GDD and ADR requirements during story closure. It catches undocumented deviations and logs technical debt for advisory changes to maintain sprint velocity.

Can I automate code review gates for QA leads and lead programmers?▼

Yes, you can automate code review gates by spawning QA lead and lead programmer review gates based on configured review mode. This ensures stories pass test coverage and receive proper code review before status update.

What is the best way to surface the next ready story after completing a sprint task?▼

Surface the next ready story by running automated end-of-story completion verification. After confirming acceptance criteria pass and documenting deviations, the next priority story is immediately identified to maintain sprint momentum.

Does story closure work for game development scenarios using GDD requirements?▼

Story closure works for game development scenarios by enforcing test evidence requirements based on story type. It cross-references implementation against GDD and ADR requirements to catch deviations in Logic, Integration, and Visual/Feel story categories.

Why does incomplete story closure create technical debt in sprint management?▼

Incomplete story closure creates technical debt by missing acceptance criteria, leaving design deviations undocumented, and skipping code reviews. Automating completion verification eliminates these risks and maintains sprint velocity through proper tech debt tracking.

Related Skills

Explore More Software Engineering Skills→
emcconnellemcconnell

story-done

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

Community
Advanced
CarlosQ96CarlosQ96

story-done

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

Community
Advanced
MichaelSolatiMichaelSolati

story-done

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

Community
Advanced
HechaoYannetHechaoYannet

story-done

Verify story completion against acceptance criteria, ADR/GDD references, and DoD.

Community
Advanced