skills.rest
AlexanderNarbaev
AlexanderNarbaevCOMMUNITY
Explore all skills by this author →
𝕏@alex_foullyGitHub

critic-gate

Enforces critic review of plans with revision loops before execution begins.

Updated May 31, 2026
Search Tags:#approval gate#plan review#spec drift#revision loop#swarm workflow#critic agent
One-click install
npx skills add https://github.com/AlexanderNarbaev/agi --skill critic-gate-alexandernarbaev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: critic-gate
Source: https://github.com/AlexanderNarbaev/agi/tree/main/.opencode/skills/critic-gate
Command: npx skills add https://github.com/AlexanderNarbaev/agi --skill critic-gate-alexandernarbaev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents unreviewed implementation plans from reaching execution by routing every plan through a critic agent verdict, revision cycles, and hard-stop checklists. ## Core Features & Use Cases - Plan Review Gate: Delegates the full plan.md and codebase context to the active swarm's critic agent and branches on APPROVED, NEEDS_REVISION, or REJECTED verdicts. - Bounded Revision Loops: Allows up to two revision-and-resubmit cycles before requiring user intervention on rejection. - Spec Drift Guard: Blocks save_plan and related tools when spec-staleness.json exists, forcing the user to run /swarm clarify or acknowledge the drift. - Use Case: After drafting .swarm/plan.md for a multi-phase feature, the architect runs this gate once; the critic flags a missing migration step, the plan is revised and resubmitted, and only then does execution begin. ## Quick Start Ask the architect to run the critic gate on the newly written .swarm/plan.md before starting any implementation.

Frequently Asked Questions about critic-gate

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

FAQPage Schema
How do I get a plan reviewed before execution in an agent swarm?▼

Run the critic gate once after writing the complete .swarm/plan.md. It sends the plan and codebase context to the swarm's critic agent, which returns APPROVED, NEEDS_REVISION, or REJECTED before any implementation starts.

How many plan revision cycles does the critic gate allow?▼

The gate allows a maximum of two revision-and-resubmit cycles when the critic returns NEEDS_REVISION. A REJECTED verdict at any cycle stops the flow and requires informing the user for guidance.

Why does save_plan reject my call with a spec gate error?▼

save_plan rejects the call when .swarm/spec.md does not exist. Verify the spec with lint_spec first, or create one using /swarm specify before attempting to save the plan.

What happens when spec-staleness.json exists in the swarm directory?▼

The runtime structurally blocks save_plan, update_task_status, phase_complete, and lock acquisition tools. The architect must surface the drift to the user, who then runs /swarm clarify or /swarm acknowledge-spec-drift.

Can the architect acknowledge spec drift itself to unblock tools?▼

No. The architect must not run /swarm acknowledge-spec-drift through any tool, chat fallback, or shell invocation. Only the user can acknowledge drift; self-invocation is treated as a control bypass and refused.

Related Skills

Explore More Software Engineering Skills→
B0yZ4kr14B0yZ4kr14

speckit-iterate-apply

Apply pending iteration plans to specification artifacts in dependency order.

Community
Advanced
CurtisTheCurtisThe
4

tdd-spike-implement

Execute spike plan phases serially with human review gates.

Community
Advanced
auleewilliamsauleewilliams

speckit-analyze

Detect inconsistencies across spec.md, plan.md, and tasks.md files.

Community
Advanced
rolopez23rolopez23

simplify

Review staged code diffs and apply conservative refactors with human sign-off.

Community
Intermediate