critic-gate

Enforces critic review and approval of plans before execution begins.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/pandejesal/drone-nav-sar --skill critic-gate-pandejesal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: critic-gate
Source: https://github.com/pandejesal/drone-nav-sar/tree/main/.swarm/bundled-skills/critic-gate
Command: npx skills add https://github.com/pandejesal/drone-nav-sar --skill critic-gate-pandejesal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents unreviewed implementation plans from reaching execution by requiring a formal critic verdict, revision loops, and a recorded approval before any coder is dispatched. ## Core Features & Use Cases - Plan Critic Review: Delegates the full plan.md and codebase context to the swarm's critic agent and handles APPROVED, NEEDS_REVISION (max 2 cycles), and REJECTED verdicts. - Approval Verification & Escape Hatch: Confirms the recorded approval via get_approved_plan before dispatch, with an audited manual override (approve_plan_critic) when the mechanical recorder fails. - Spec Gates & Traceability: Enforces SPEC-GATE before save_plan, blocks tools on spec staleness drift, and requires every MUST/SHALL SC-### obligation to map to plan tasks. - Use Case: An architect agent writes .swarm/plan.md, runs CRITIC-GATE once, gets an APPROVED verdict recorded, and only then dispatches coders in MODE: EXECUTE without hitting PLAN_CRITIC_GATE_VIOLATION. ## Quick Start Ask the architect agent to run the critic-gate protocol 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 run the critic gate on a plan before execution?

Run CRITIC-GATE once when you first write the complete .swarm/plan.md. Send the full plan content and codebase context to the swarm's critic agent, referencing plan.md or critic-gate in the dispatch prompt so the approval is recorded.

What is a PLAN_CRITIC_GATE_VIOLATION error?

It means a coder was dispatched without a recorded plan_critic_gate approval snapshot. Call get_approved_plan to verify the verdict was recorded; if the APPROVED verdict was lost, re-run CRITIC-GATE or use approve_plan_critic with a reason as a manual override.

How many revision cycles does the critic gate allow?

The gate allows a maximum of 2 revision cycles. A NEEDS_REVISION verdict requires revising the plan and resubmitting; a REJECTED verdict at any cycle stops the process and requires informing the user for guidance.

Why is save_plan rejected with SPEC_REQUIRED?

save_plan enforces SPEC-GATE: it rejects calls when /swarm sdd status reports no resolved effective spec. Generate a spec first via /swarm specify or /swarm sdd project, or override with SWARM_SKIP_SPEC_GATE=1.

What happens when spec staleness drift is detected?

The runtime structurally blocks tools like save_plan and update_task_status while .swarm/spec-staleness.json exists. The architect must surface the drift to the user, who resolves it with /swarm clarify or /swarm acknowledge-spec-drift.

When should the manual approve_plan_critic override be used?

Use it only when the critic genuinely returned APPROVED but the mechanical recorder failed to persist the snapshot, and re-running CRITIC-GATE does not help. It records an audited manual_override approval and is not a substitute for an actual critic review.