brain-review-gate

Validate worker output against beads state and audit requirements.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/getspur/spur --skill brain-review-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: brain-review-gate
Source: https://github.com/getspur/spur/tree/main/.spur/skills/brain-review-gate
Command: npx skills add https://github.com/getspur/spur --skill brain-review-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents the approval of incomplete or unverified agent work by enforcing a strict, evidence-based review process that ensures all changes are properly recorded in the beads system.

Core Features & Use Cases

  • Audit Trail Verification: Automatically validates that worker output is backed by required audit sentinels and status transitions.
  • Signal Handling: Detects and manages critical signals like scope drift, blocking issues, and risk flags before integration.
  • Use Case: Use this during a multi-agent coding session to ensure that a worker's proposed diff is fully consistent with the project's state and that no invisible work is merged into the staging branch.

Quick Start

Run the brain-review-gate skill to verify the current worker output against the beads issue status and audit trail before approving the changes.

Frequently Asked Questions about brain-review-gate

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

FAQPage Schema
How do I enforce code review gates in a multi-agent workflow?

Code review gates in a multi-agent workflow are enforced by validating worker output against audit requirements and beads state. This ensures unverified code integration is prevented by requiring strict adherence to signal-based decision making before task completion.

What is a beads-first invariant in multi-agent orchestration?

A beads-first invariant in multi-agent orchestration requires strict adherence to the beads system state to prevent invisible work. It validates that all worker output is backed by required audit sentinels and status transitions before integration into staging.

How do I validate audit trails for agent output before merging?

Audit trails for agent output are validated by checking worker diffs against required audit sentinels and status transitions. This process ensures the proposed changes are fully consistent with the project state before approving them for staging.

Can I use human-in-the-loop review for multi-agent coding sessions?

Yes, human-in-the-loop review is supported for multi-agent coding sessions where task completion requires strict evidence-based review. It detects scope drift and blocking issues to prevent unverified code from merging into staging branches.

How does signal handling manage scope drift in multi-agent orchestration?

Signal handling manages scope drift in multi-agent orchestration by detecting and managing critical risk flags before integration. This prevents incomplete agent work from being approved when scope drift or blocking issues are present in the worker output.

When should I not use automated review gates for agent output?

Automated review gates for agent output should not be used when the multi-agent workflow lacks beads state tracking or audit trail requirements. Without these prerequisites, signal-based decision making cannot properly validate worker output consistency.