story-done

Verify acceptance criteria, ADR/CDD conformance, and update story status.

3|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill story-done-negentropy-laby
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/Negentropy-Laby/Constitution-Driven-Development/tree/main/.agents/skills/story-done
Command: npx skills add https://github.com/Negentropy-Laby/Constitution-Driven-Development --skill story-done-negentropy-laby

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-to-end story completion validation is often manual and error-prone. This skill automates the verification of acceptance criteria, ADR/CDD conformance, and status updates to ensure a story is truly complete before closure.

Core Features & Use Cases

  • Verifies acceptance criteria against implemented code and references ADR/CDD constraints.
  • Prompts for code review and surfaces the next ready story from the sprint.
  • Updates the story status to Complete and logs completion notes for auditability and governance.

Quick Start

Run the command on the active story path or supply a specific story file path to execute the end-of-story 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 ADR conformance before closing a story?

Story completion validation verifies acceptance criteria against implemented code and checks ADR/CDD constraints to ensure a story is truly complete before closure. It automates these governance checks to reduce manual errors.

What is the best way to automate end-of-story workflow checks for sprint governance?

Automating end-of-story workflow checks involves validating completion criteria, prompting code reviews, and updating story status. This guided process ensures readiness and logs completion notes for auditability.

How do I update story status and generate completion logs for auditability?

Updating story status to Complete and generating completion logs provides traceability for auditability. The workflow validates conformance and records completion notes during the end-of-story process.

Can I prompt for code reviews and surface the next ready story during story closure?

Yes, the story closure workflow prompts for code reviews and surfaces the next ready story from the sprint. This ensures continuous flow while verifying acceptance criteria and governance constraints.

Does end-to-end story completion validation work without external dependencies?

End-to-end story completion validation operates with no external dependencies. It applies project governance tasks across software and product stories through guided prompts for readiness verification.

Why does manual story closure fail to ensure traceability and governance compliance?

Manual story closure fails traceability because it is error-prone and often misses ADR/CDD conformance checks. Automating the verification of acceptance criteria ensures true readiness before status updates.