failure-criteria

Enforces predefined stop conditions across builds, tests, APIs, and dependencies.

6|Updated Feb 20, 2025
One-click install
npx skills add https://github.com/zerobias-org/module --skill failure-criteria
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: failure-criteria
Source: https://github.com/zerobias-org/module/tree/main/.claude/skills/failure-criteria
Command: npx skills add https://github.com/zerobias-org/module --skill failure-criteria

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prevents wasted effort by halting work immediately when predefined failure criteria are met, ensuring teams stop unsafe or non-compliant work early.

Core Features & Use Cases

  • Enforces stop conditions across critical gates (naming, API responses, tests, builds, and dependencies)
  • Guides teams through mandatory checks to maintain quality, compliance, and process discipline
  • Use Case: In API development, automatically halt progress if an API spec includes 4xx/5xx responses or tests are missing

Quick Start

Run the failure-criteria checks before starting any implementation to ensure all gates are satisfied.

Frequently Asked Questions about failure-criteria

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

FAQPage Schema
How do I enforce immediate failure conditions to halt non-compliant builds?

You can enforce immediate failure conditions by validating required checks across tests, builds, and dependency locks, which halts work immediately when critical governance gates are not satisfied to prevent wasted effort.

What are quality gates in API development and when do I need them?

Quality gates in API development are mandatory validation checks that stop work when critical conditions are met. You need them to prevent unsafe progress, such as when an API spec includes 4xx/5xx responses or tests are missing.

How do I set up stop conditions for code quality and environment hygiene?

Set up stop conditions by specifying and validating required checks for naming conventions, test presence, build verification, dependency locking, and environment hygiene to maintain process discipline and compliance across software engineering tasks.

Can I use failure criteria to halt progress if API error handling is missing?

Yes, you can halt progress in API development workflows if an API spec includes 4xx/5xx responses or if required tests are missing, ensuring teams stop unsafe or non-compliant work early before proceeding further.

Why should I run failure criteria checks before starting an implementation?

Running failure criteria checks before implementation ensures all governance gates are satisfied upfront, preventing wasted effort by halting work immediately when predefined failure conditions like missing builds or incorrect naming are detected.