Gatekeeper

Validate project phase readiness against required artifacts and quality criteria.

Updated Dec 9, 2025
One-click install
npx skills add https://github.com/paulojoseph/next-generation-aec --skill gatekeeper
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Gatekeeper
Source: https://github.com/paulojoseph/next-generation-aec/tree/main/.claude/skills/gatekeeper
Command: npx skills add https://github.com/paulojoseph/next-generation-aec --skill gatekeeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Gatekeeper skill prevents progression to the next phase until all prerequisites, artifacts, and quality criteria are complete, ensuring deterministic governance of workflows.

Core Features & Use Cases

  • Automated phase validation: checks prerequisites, artifacts, and quality criteria for each workflow gate.
  • Traceable decisions: records gate outcomes and surfaces actionable gaps to unblock progress.
  • Use Case: when a phase completes, Gatekeeper validates readiness before advancing, preventing regression and misalignment with specs.

Quick Start

Use the Gatekeeper to validate the current phase, review the gate report, and address any blockers before moving to the next phase.

Frequently Asked Questions about Gatekeeper

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

FAQPage Schema
How do I validate phase readiness before advancing a software project workflow?

To validate phase readiness, enforce automated quality gates that check for required artifacts, missing references, and insufficient documentation. Gatekeeper evaluates completion against specifications and produces a clear pass/fail result with actionable gaps to unblock progress.

What is a quality gate in workflow validation and how does it prevent premature progression?

A quality gate in workflow validation is an automated checkpoint that enforces specification-driven completion of required artifacts before advancing. It prevents premature progression by detecting placeholders and missing references, updating task state to block phase advancement until criteria are met.

How to detect placeholders and missing references in project artifacts before moving to the next phase?

Detect placeholders and missing references by applying specification-driven quality gates to each phase transition. Gatekeeper scans required artifacts against quality criteria, identifying incomplete documentation and surfacing actionable gaps in a traceable gate report before progression is permitted.

Can I enforce specification alignment automatically when a project phase completes?

Yes, you can enforce specification alignment automatically when a phase completes by applying automated quality gates. Gatekeeper validates that all prerequisites and artifacts strictly align with project specs, generating a pass/fail outcome that prevents regression and misalignment before advancing.

What's the best way to set up deterministic governance for software engineering phase transitions?

The best way to set up deterministic governance for phase transitions is to implement strict, specification-driven quality gates. Gatekeeper enforces deterministic workflow governance by validating all prerequisites and quality criteria at each gate, ensuring no phase advances without complete artifact readiness.

Why does a project phase fail validation and how do I surface actionable gaps?

A project phase fails validation when required artifacts contain placeholders, missing references, or insufficient documentation. Gatekeeper surfaces these actionable gaps in a traceable gate report, recording the gate outcome to unblock progress by clearly identifying what must be addressed before advancing.