Story Done

Story Done

argument-hint: "[story-file-path] [--review full|lean|solo]"

Category: design Source: Donchitos/Claude-Code-Game-Studios

Story Done: End-of-Story Completion Review for Happycapy Skills

What Is This

The Story Done skill (story-done) is an automated, user-invocable tool designed for the Happycapy Skills platform. Its primary function is to formalize and enforce the final review process at the end of implementing a story. The skill reads a specified story file, verifies that all acceptance criteria are met by the implementation, checks for any deviations from the Game Design Document (GDD) or Architectural Decision Records (ADR), prompts for a code review, updates the story status to "Complete," and identifies the next story ready for development within the current sprint. The skill seamlessly integrates with project workflows by leveraging file operations and command-line arguments, ensuring design and engineering teams maintain high standards of traceability and accountability.

Why Use It

In many development workflows, stories can be prematurely marked as done, often skipping critical steps such as acceptance verification, code review, or documentation of design changes. This leads to technical debt, misaligned features, and incomplete or buggy software. The Story Done skill mitigates these risks by:

  • Systematically verifying each acceptance criterion against the actual implementation
  • Ensuring any deviations from GDD or ADR are explicitly documented
  • Prompting for required code reviews
  • Automatically updating the story's status to "Complete" only when all checks pass
  • Surfacing the next ready story, improving team flow and minimizing idle time

By automating these checks, the skill enforces discipline in the development process and significantly reduces the chance of overlooked requirements or undocumented changes.

How to Use It

Arguments and Invocation

The skill is invoked via the command line as follows:

/story-done [story-file-path] [--review full|lean|solo]
  • story-file-path: (Optional) Path to the story file to review and complete. If omitted, the skill will attempt to locate the active story automatically.
  • --review: (Optional) Specifies the review mode. Accepts full, lean, or solo.

Review Mode Resolution

The skill determines the review mode in the following order:

  1. If --review is provided in the command, that value is used.
  2. Otherwise, it reads the review mode from production/review-mode.txt.
  3. If neither is set, it defaults to lean.

Story File Resolution

  • If a file path is provided, the skill reads that file directly.
  • If no file path is specified, the skill checks production/session-state/active.md for the currently active story.
  • If there is no active story, it selects the most recently modified story file.

Main Functional Steps

  1. Read and Parse the Story File: Loads the story and extracts acceptance criteria.
  2. Verify Acceptance Criteria: For each criterion, checks the codebase to ensure it is implemented and working as intended. This may involve pattern matching, code inspection, or running test commands.
  3. Check for GDD/ADR Deviations: Compares the implementation to the documented GDD and ADRs. If deviations are detected, prompts the user to document them rather than allowing silent changes.
  4. Prompt for Code Review: Based on the review mode, prompts team members for a code review or, in solo mode, confirms individual review steps.
  5. Update Story Status: Modifies the original story file, marking the status as "Complete."
  6. Surface Next Story: Identifies and outputs the next story that is ready to be worked on, streamlining workflow continuity.

Example Usage

/story-done production/epics/core/story-damage-calculator.md --review full

This command will perform a full review on the specified story, updating its status and surfacing the next story.

Sample Story File Update

## Story: Damage Calculator
...
Status: Complete
...

When to Use It

Invoke the Story Done skill at the end of implementing any story, before it is considered complete in your project management system. It is particularly valuable in the following scenarios:

  • Before merging a feature branch to ensure all requirements are satisfied
  • When preparing for sprint completion or release candidates
  • During code freeze periods, to ensure all stories are fully reviewed and documented
  • Whenever team members need to validate that no steps in the definition of done are missed

Important Notes

  • The skill enforces a strict completion checklist, minimizing the risk of skipped steps or undocumented changes.
  • It is user-invocable, supporting both individual and team workflows.
  • Only English is supported - do not use Chinese characters or emojis.
  • Review modes allow flexibility: full for comprehensive team reviews, lean for lightweight checks, and solo for single-developer flows.
  • Adherence to the order of review mode resolution and story file selection is critical for consistent operation.
  • The skill relies on up-to-date GDD and ADR documentation; ensure these references are maintained for accurate deviation checks.
  • All modifications to story files are tracked, providing an auditable history of status changes and review outcomes.

By integrating the Story Done skill into your development workflow, you ensure every story is robustly reviewed, properly documented, and truly complete before moving on to the next task.