gate

Enforce mandatory development lifecycle checkpoints with evidence and compliance validation.

3|Updated Sep 27, 2025
One-click install
npx skills add https://github.com/Sheldon-92/TAD --skill gate-sheldon-92
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gate
Source: https://github.com/Sheldon-92/TAD/tree/main/.agents/skills/gate
Command: npx skills add https://github.com/Sheldon-92/TAD --skill gate-sheldon-92

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Gate enforces mandatory checkpoints across the development lifecycle, ensuring that each stage—requirements elicitation, design, implementation, and handoff—meets predefined criteria before progression.

Core Features & Use Cases

  • Enforces four gates (Gate 1–Gate 4) with blocking rules to prevent progression until criteria are met.
  • Validates evidence, handoff readiness, and §9.1 Spec Compliance checklist, including rubric-based verifications.
  • Provides a standardized gate-verdict process and post-pass actions to ensure traceability and compliance.

Quick Start

Run the gate quality gate at the appropriate stage to validate readiness and block progression until criteria are satisfied.

Frequently Asked Questions about gate

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

FAQPage Schema
How do I enforce quality gates across the continuous delivery lifecycle?

Quality gates enforce mandatory checkpoints across the continuous delivery lifecycle by validating evidence, handoff readiness, and spec compliance to block progression until criteria are satisfied.

What is a quality gate in the software development lifecycle?

A quality gate is a mandatory checkpoint mechanism that validates evidence, handoff readiness, and spec compliance to block progression until criteria are satisfied across development stages.

How do I block code progression before spec compliance is verified?

You can block code progression by applying a gate enforcement process that requires active handoff metadata, completion artifacts, and rubric outputs to verify spec compliance before passing a stage.

Does continuous delivery require handoff metadata to pass a quality gate?

Yes, continuous delivery requires active handoff metadata and completion artifacts to drive gate enforcement, validate readiness, and determine pass/fail verdicts before stage progression.

What's the best way to automate code review checkpoints for stage handoff?

The best way to automate code review checkpoints is using a standardized gate-verdict process that requires rubric-based verifications and completion artifacts to determine pass/fail status before stage handoff.

Why does my development pipeline not block progression when evidence is missing?

Your pipeline lacks a blocking gate mechanism that requires completion artifacts and active handoff metadata to validate evidence before allowing progression to the next stage.