completion-criteria

Validate software feature completion against quality gates for API, code, tests, build, and dependencies.

6|Updated Feb 20, 2025

Search Tags:#automation #testing #documentation #completion #build #lint #quality-gates

Ready to run

npx skills add https://github.com/zerobias-org/module --skill completion-criteria

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: completion-criteria
Source: https://github.com/zerobias-org/module/tree/main/.claude/skills/completion-criteria
Command: npx skills add https://github.com/zerobias-org/module --skill completion-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable checklist to determine when software work is truly complete, preventing scope creep and missed validation.

Core Features & Use Cases

Gate-driven completion: a multi-phase checklist spanning API spec alignment, code generation, testing, building, and release readiness.
Enforcement & governance: automatic detection of missing tests, build issues, or outdated dependencies before shipping.
Use Case: teams can adopt this to ensure every release passes all gates before merge or deployment.

Quick Start

Run the completion-criteria validator after implementing a feature to verify all gates are satisfied and documented.

Frequently Asked Questions about completion-criteria

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

FAQPage Schema

How do I automate end-to-end validation for software feature completion before release?▼

You can enforce release readiness by running a multi-phase quality gate checklist that validates API spec accuracy, generated code, test coverage, build integrity, and dependency locking before shipping software features.

What is a gate-driven completion checklist for API development and testing?▼

Gate-driven completion is a structured quality gate framework that spans API spec alignment, code generation, testing, building, and release readiness to automatically detect missing tests, build issues, or outdated dependencies.

How do I prevent scope creep and missed validation during code generation workflows?▼

Prevent scope creep by enforcing automated quality gates after implementing a feature, verifying that generated code, API specs, and test coverage meet completion criteria before merge or deployment.

Does the completion validation framework support dependency locking and build integrity checks?▼

Yes, the completion validation framework enforces dependency locking and build integrity checks as part of its comprehensive quality gates to ensure release readiness and prevent shipping broken builds or outdated dependencies.

What's the best way to enforce quality gates for API spec accuracy before deployment?▼

The best way to enforce quality gates for API spec accuracy is to run an automated validator after feature implementation to verify spec alignment, test coverage, and build integrity are satisfied and documented before deployment.