gatekeeper-design

Audits design documents and outputs structured reports with severity-ranked fixes and routing verdicts.

9|Updated Apr 12, 2026
One-click install
npx skills add https://github.com/TykoDev/SupremeTeam --skill gatekeeper-design
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gatekeeper-design
Source: https://github.com/TykoDev/SupremeTeam/tree/main/skills/design/gatekeeper-design
Command: npx skills add https://github.com/TykoDev/SupremeTeam --skill gatekeeper-design

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Gatekeeper-design prevents low-quality or inconsistent design deliverables from advancing in the development pipeline by applying an adversarial review that surfaces factual errors, contradictions, omissions, and feasibility problems before handover.

Core Features & Use Cases

  • Adversarial review: Systematic, skeptical examination of architecture docs, requirements, project plans, implementation specs, and frontend specifications to find real problems.
  • Structured findings & verdicts: Classifies issues as CRITICAL/MAJOR/MINOR, issues APPROVED/REVISE/ESCALATE verdicts, and provides mandatory fixes and re-review scope.
  • Pipeline-aware operation: Supports pipeline mode (commander-owned review loop) and standalone mode (direct specialist or user reviews) with explicit routing and save-awareness.
  • Use Case: Validate an architecture document against stack-lock constraints and produce a GATEKEEPER REVIEW REPORT listing required fixes and an approval condition checklist.

Quick Start

Review the attached architecture document with stack-lock context and produce a GATEKEEPER REVIEW REPORT that lists findings by severity, required fixes, and a final verdict.

Frequently Asked Questions about gatekeeper-design

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

FAQPage Schema
What is an adversarial design review for architecture documents?

It systematically examines architecture documents and implementation specifications to surface factual errors, contradictions, omissions, and feasibility problems before project handover.

How do I perform a quality gate review on project plans and requirements?

You perform a quality gate review by validating project plans and requirements against stack-lock constraints, which classifies issues by severity and produces a structured findings report with mandatory fixes and a final approval verdict.

Can I use design review to check frontend and backend specifications against stack-lock constraints?

Yes, design review can validate both frontend and backend specifications against stack-lock context, producing a structured findings report that issues APPROVED, REVISE, or ESCALATE verdicts based on classified issue severities.

How does pipeline-aware design review work for deliverable routing?

Pipeline-aware design review operates in either commander-owned pipeline mode or standalone mode, consuming deliverable content and metadata to generate routing instructions for approval or escalation based on a numeric quality score.

What is the best way to prevent inconsistent design deliverables from advancing in the development pipeline?

The best way to prevent inconsistent deliverables from advancing is applying an adversarial review that issues mandatory fixes and re-review scope, ensuring low-quality architecture documents fail the quality gate before handover.