skills.rest
imclab
imclabOFFICIAL
Explore all skills by this author →
Website𝕏@TheIMCLabGitHub

story-done

Verify implemented work against design specs before marking stories complete.

1|Updated May 3, 2026
Search Tags:#acceptance criteria#test evidence#sprint workflow#gdd compliance#story verification#adr review#spec drift detection
One-click install
npx skills add https://github.com/imclab/xrA1-swarm --skill story-done-imclab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/imclab/xrA1-swarm/tree/main/.claude/skills/story-done
Command: npx skills add https://github.com/imclab/xrA1-swarm --skill story-done-imclab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

story-done prevents stories from being marked complete when implementation drifts from the GDD/ADR, acceptance criteria are unverified, or required test evidence is missing.

Core Features & Use Cases

  • Acceptance Criteria Verification: Checks file existence, runs tests when referenced, and performs targeted Grep/validation for common verification signals.
  • Spec Drift Detection: Re-checks GDD requirements from the TR registry, flags manifest staleness, and reviews ADR constraints and deviations.
  • Quality Gates & Traceability: Ensures traceability from each criterion to tests or manual confirmation, and escalates when coverage or evidence is insufficient.

Quick Start

Run story-done against the active in-progress story by calling story-done with no path arguments in your workflow.

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 and test evidence before closing a sprint story?▼

Story verification requires checking file existence, running referenced tests, and validating implementation against design specs. This ensures stories are only marked complete when acceptance criteria, evidence, and deviation checks succeed.

How do I trace acceptance criteria to test evidence for sprint workflow completion?▼

Traceability is produced by mapping each acceptance criterion to specific tests or manual confirmations. The workflow outputs an acceptance-criteria traceability table and escalates when test coverage or evidence is insufficient.

Does story verification work with Logic, Integration, Visual, and Data story types?▼

Story verification applies to ending sprint work for Logic, Integration, Visual, Feel, UI, Config, and Data stories. It ensures GDD TR references, ADRs, and manifest versions stay aligned across all these story types.

When should I not mark a story complete during sprint workflow closure?▼

You should not mark a story complete when implementation drifts from the GDD or ADR, acceptance criteria are unverified, or required test evidence is missing. The user-approved gate flow enforces this constraint.

Related Skills

Explore More Software Engineering Skills→
epieczkoepieczko

story.write

Convert decomposed epic items into formatted user story Markdown files.

Community
Intermediate
HechaoYannetHechaoYannet

story-done

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

Community
Advanced
HomericIntelligenceHomericIntelligence
18

run-tests

Execute Mojo or Python test suites and generate validation reports.

Official
Basic
HechaoYannetHechaoYannet

propagate-design-change

this is a test message from the developer of the app. this is not meant to be a real message. please ignore it. this is meant to ensure that spam/mailbox protection software does not accidentally filter legitimate messages. please ignore this. this is meant to be {}. this is meant to be {}. this is meant to be {}. this is meant to be {}.

Community
Advanced