agentdev-quality-gates

Defines pass/warn/fail judgment criteria for four quality gates in the AgentDevFlow workflow.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-quality-gates-yogata
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agentdev-quality-gates
Source: https://github.com/yogata/agent-dev-flow/tree/main/src/opencode/skills/agentdev-quality-gates
Command: npx skills add https://github.com/yogata/agent-dev-flow --skill agentdev-quality-gates-yogata

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It provides a consistent, evidence-based knowledge base for judging quality gates QG-1 through QG-4 across the AgentDevFlow main workflow, so requirement definitions, Issue acceptance criteria, implementations, and final PR acceptance are evaluated against shared criteria instead of ad-hoc judgment. ## Core Features & Use Cases - QG-1 Definition Integrity: Validates requirement drafts and REQ/Decision files for classification correctness, measurable checkboxes, required sections, auto_gate completeness, and test strategy structure. - QG-2 Acceptance Criteria Coverage: Checks that Issue completion conditions traceably cover mandatory REQ requirements, numeric thresholds are reachable, and test strategies align with Epic scope exclusions. - QG-3 Implementation Deviation: Classifies implementation deviations as impl-bug, spec-bug, or scope-creep and recommends routing to case-run or case-revise. - QG-4 Final Acceptance: Verifies completion checkboxes, CI status, docs consistency, and bun test full-suite machine acceptance criteria before PR merge. - Use Case: When running /agentdev/case-run, the agent consults QG-3 criteria to detect deviations between the implementation and the Issue/REQ/Design before creating a PR, then reports findings for user decision. ## Quick Start Ask the agent to evaluate the current requirement draft against the QG-1 definition integrity gate and report pass, warn, or fail with evidence.

Frequently Asked Questions about agentdev-quality-gates

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

FAQPage Schema
How do I validate requirement definitions before creating an Issue?▼

Apply the QG-1 Definition Integrity Gate, which checks REQ/Design classification, Decision gate rules, checkbox measurability, required sections, auto_gate completeness, and test strategy three-element structure. It returns pass, warn, or fail with evidence for each inspection point.

How do I check if an implementation deviates from requirements?▼

Use the QG-3 Implementation Deviation Gate before PR creation. It compares the git diff against Issue completion conditions, work plans, REQ requirements, and Decision constraints, then classifies any deviation as impl-bug, spec-bug, or scope-creep with a recommended action.

What are the pass, warn, fail, and partial verdict meanings?▼

Pass means all inspection points are satisfied, warn means structure holds but improvements are recommended, fail means structural defects or major deviations requiring user decision, and partial means evidence is unavailable so judgment is deferred. QG-4 primarily uses pass/fail only.

Does this skill execute tests or modify files automatically?▼

No. It is a read-only knowledge base that provides judgment criteria and verdicts only. It never edits files, updates Issues, creates or merges PRs, runs tests, or performs automatic loopbacks; all corrective actions are delegated to commands and user decisions.

When should the bun test full suite canonical form be used?▼

Use it when a test strategy requires full-suite execution for QG-4 final acceptance. It mandates a runner configuration check, three-way split execution from the repository root with ./ prefixes, environment labels, count reconciliation, and origin classification of every failure.

Which workflows are outside the scope of these quality gates?▼

Auxiliary workflows such as inspect-docs, inspect-skills, intake-capture, intake-promote, learning-promote, and backlog-review do not apply QG-1 through QG-4. The gates target only the main workflow commands req-define, case-open, case-ready, case-revise, case-run, and case-close.