Verify development story completion against acceptance criteria and governance artifacts.
npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill story-done-wsman
Please help me install this Agent Skill. Skill: story-done Source: https://github.com/wsman/MY-DOGE-MICRO/tree/main/.agents/skills/story-done Command: npx skills add https://github.com/wsman/MY-DOGE-MICRO --skill story-done-wsman
This Skill removes the uncertainty from ending a development story by checking that the work actually matches the acceptance criteria, governance rules, and implementation evidence before anything is marked complete.
Use the story-done skill to review the specified story file and determine whether it is ready to be marked Complete.
High-intent search queries and answers about installing and using this skill.
Verifying acceptance criteria before story closure requires reviewing implementation evidence, test coverage, and code reviews against project artifacts. This validation process ensures completion status is determined by concrete evidence rather than assumptions before marking work as done.
ADR compliance during story review is checked by comparing completed development work against architecture records and manifests. This process flags governance deviations, scope gaps, and test coverage issues so risks remain visible before finalizing story completion status.
End-of-story QA validation involves assessing test coverage evidence, prompting code reviews, and checking implementation against governance rules. This workflow validates that completed code meets acceptance criteria and project artifacts before safely closing the story.
Validating development story completion requires a story file alongside architecture, ADR, sprint, and session artifacts. These inputs enable the review process to check implementation evidence, verify acceptance criteria, and update completion status based on concrete project data.
Surfacing the next ready story after closure is supported through completion workflow features that update story status and preserve sprint and session state. This workflow records completion notes and maintains team continuity by identifying subsequent ready stories.
Story closure fails when implementation evidence does not match acceptance criteria because the validation process detects coverage gaps, scope deviations, and missing governance compliance. These checks prevent premature completion status updates by surfacing risks before final closure.
polseguVerify story implementation against acceptance criteria and design documents.
slgoodrichGenerate user story templates with acceptance criteria and INVEST validation.
cenconq25Audit per-story test coverage and documentation to identify evidence gaps.
tstaplerRequire fresh verification evidence before claiming task completion.
