done-story

Verify backend story implementations against defined task definitions and coding standards.

Updated Jul 3, 2025
One-click install
npx skills add https://github.com/HiveSpaceTeam/hivespace.microservice --skill done-story
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: done-story
Source: https://github.com/HiveSpaceTeam/hivespace.microservice/tree/main/.agent-source/skills/done-story
Command: npx skills add https://github.com/HiveSpaceTeam/hivespace.microservice --skill done-story

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates and validates the completion of backend stories against predefined task definitions, ensuring quality and adherence to standards before marking a story as done.

Core Features & Use Cases

  • Automated Verification: Checks the backend implementation against specified story requirements.
  • Comprehensive Validation: Ensures that all tasks, features, and conventions are correctly implemented.
  • Use Case: For developers working on backend stories, use this Skill to verify that their changes meet the project's quality standards before finalizing the story.

Quick Start

Run the 'done-story' command after completing your backend story to verify all backend tasks.

Frequently Asked Questions about done-story

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

FAQPage Schema
How do I verify backend story completion against task definitions?

You can verify backend story completion by running an automated validation command that checks your implementation against specified story requirements, ensuring all tasks, features, and conventions are correctly implemented before marking it done.

What is automated backend story verification?

Automated backend story verification is the process of validating implementation against predefined task definitions to ensure quality and adherence to strict backend development practices before a story is considered complete.

Does backend story validation check domain events and monetary values?

Yes, backend story validation checks domain events, monetary values, coding standards, and integration message patterns to ensure comprehensive compliance with project quality requirements.

Can I use this for projects without strict backend development practices?

This verification tool is specifically suitable for projects with strict backend development practices, as it requires checking adherence to coding standards, domain events, monetary values, and integration message patterns defined in task specifications.

What's the best way to ensure backend code meets quality standards before finalizing?

The best way to ensure backend code meets quality standards is to run an automated verification process that validates implementation against defined task definitions, checking all conventions and requirements are correctly implemented before marking the story done.