What levels of project management does this skill cover?

The skill operates at three distinct levels: the Story level (individual features), the Sprint level (periodic iterations), and the Release level (final production deployment).

How does this skill prevent technical debt?

By enforcing strict criteria such as peer reviews, unit testing, and documentation before a story is declared 'done,' it ensures that no unfinished or low-quality work is pushed forward.

Can I customize the quality criteria?

Yes, the skill is designed to be adapted to your specific project context. It provides templates that teams can modify to add or remove criteria based on their unique requirements.

What is the Definition of Done (DoD) skill?

It is a specialized Claude Code capability that helps development teams define, apply, and enforce a formal checklist of quality standards that must be met before work is considered complete.

When is the best time to trigger this skill?

It should be used when closing Phase 3, before starting Phase 4 (Iterative Delivery), during every sprint review, and whenever quality standards need updating.

Definition of Done

Name: Definition of Done
Author: nsalvacao

bynsalvacao

0•

Herramientas de Colaboración

Enforces standardized quality criteria across story, sprint, and release levels to eliminate ambiguity in software delivery.

The Definition of Done (DoD) skill provides a structured framework for teams to establish and maintain rigorous quality standards throughout the agile lifecycle. By utilizing schema-validated templates, it ensures that 'done' is clearly defined at the story, sprint, and release levels, preventing the silent accumulation of technical debt. This skill guides teams through establishing agreements, validating work during sprint reviews, and updating quality gates as project requirements evolve, making it an essential tool for maintaining high-production standards in iterative delivery.

Características Principales

010 GitHub stars

02Multi-level criteria management for Stories, Sprints, and Releases

03Schema-validated templates for standardized quality documentation

04Automated triggers for Phase 4 (Iterative Delivery) readiness assessments

05Integrated quality checks for sprint reviews and formal gate approvals

06Structured team agreement workflow for collaborative quality setting

Casos de Uso

01Conducting release readiness audits including security scans and UAT sign-offs

02Validating user stories during sprint reviews to ensure no criteria are overlooked

03Establishing team-wide quality standards before starting iterative development cycles

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add nsalvacao/nsalvacao-claude-code-plugins definition-of-done

For use in Claude.ai and ChatGPT

Características Principales

010 GitHub stars

02Multi-level criteria management for Stories, Sprints, and Releases

03Schema-validated templates for standardized quality documentation

04Automated triggers for Phase 4 (Iterative Delivery) readiness assessments

05Integrated quality checks for sprint reviews and formal gate approvals

06Structured team agreement workflow for collaborative quality setting

Casos de Uso

01Conducting release readiness audits including security scans and UAT sign-offs

02Validating user stories during sprint reviews to ensure no criteria are overlooked

03Establishing team-wide quality standards before starting iterative development cycles

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add nsalvacao/nsalvacao-claude-code-plugins definition-of-done

For use in Claude.ai and ChatGPT