story-done

Verify acceptance criteria and update story status to Complete.

Updated Feb 8, 2024
One-click install
npx skills add https://github.com/kay6198835/Game-RPG --skill story-done-kay6198835
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: story-done
Source: https://github.com/kay6198835/Game-RPG/tree/main/.claude/skills/story-done
Command: npx skills add https://github.com/kay6198835/Game-RPG --skill story-done-kay6198835

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

End-of-story completion review and status update automation. It ensures every acceptance criterion is verified, GDD/ADR deviations are surfaced, code-review prompts are triggered, and the story status is updated to Complete, while surfacing the next ready story from the sprint.

Core Features & Use Cases

  • Read the story file and verify each Acceptance Criterion against the implementation.
  • Surface GDD/ADR deviations explicitly and prompt for code review before closure.
  • Update the story to Complete and surface the next ready story from the current sprint.

Quick Start

Provide a story file path to run the completion process and surface the next sprint-ready story.

Frequently Asked Questions about story-done

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate story completion verification against acceptance criteria?

Story completion verification works by reading a story file, validating each acceptance criterion against the implementation, and updating the story status to Complete. It explicitly surfaces GDD/ADR deviations and triggers code-review prompts before closure.

How do I surface GDD and ADR deviations before closing a sprint story?

Surfacing GDD and ADR deviations requires running the end-of-story completion process on a provided story file. It explicitly identifies deviations, prompts for code review, and updates the story to Complete while surfacing the next ready sprint story.

What is the best way to update story status to Complete and surface the next ready story?

The best way to update story status to Complete is using an automated completion process that reads the story file, verifies acceptance criteria, and surfaces the next ready story from the current sprint. It supports optional review modes for flexibility.

Does the story completion process prompt for code review before closure?

Yes, the story completion process explicitly prompts for code review before closure. It validates acceptance criteria, surfaces GDD/ADR deviations, and triggers the code-review prompts as part of updating the story status to Complete.

How do I trigger end-of-story completion using a story file path?

To trigger end-of-story completion, provide a story file path to run the completion process. The system verifies acceptance criteria, surfaces GDD/ADR deviations, updates the story to Complete, and surfaces the next sprint-ready story.