slb

Coordinate two-person peer review for destructive commands in multi-agent workflows.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Dunc4nJ/agent-skills --skill slb-dunc4nj
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: slb
Source: https://github.com/Dunc4nJ/agent-skills/tree/main/skills/slb
Command: npx skills add https://github.com/Dunc4nJ/agent-skills --skill slb-dunc4nj

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Simultaneous Launch Button (SLB) enforces a two-person review barrier for potentially destructive commands in multi-agent workflows, preventing irreversible actions by requiring explicit peer approval before execution.

Core Features & Use Cases

  • Peer-reviewed execution: commands associated with risky actions must be approved by a second reviewer.
  • Client-side enforcement: commands execute in the user's shell environment with environment inheritance preserved.
  • Risk-tier classification & hash binding: automated risk tiering and SHA-256 command binding to detect tampering.
  • Five execution gates & audit logs: five checks before execution plus detailed logs for traceability.
  • Use cases: safe automation of dangerous ops in CI/CD, infrastructure changes, and sensitive data operations in multi-agent coding environments.

Quick Start

Install SLB and start a session to begin reviewing and approving risky commands.

Frequently Asked Questions about slb

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

FAQPage Schema
How do I enforce two-person approval for destructive commands in a multi-agent workflow?

Two-person approval for destructive commands is enforced by requiring explicit peer review before execution, using risk-tier classification and SHA-256 command binding to prevent unauthorized or tampered actions in multi-agent sessions.

What is a two-person safety guard for risky infrastructure changes, and when do I need it?

A two-person safety guard for risky infrastructure changes requires a second reviewer to approve potentially destructive commands before they run, needed when automating dangerous operations like data deletion or system config modifications.

How does client-side command validation work for parallel AI agent sessions?

Client-side command validation for parallel AI agent sessions works by executing commands in the user's shell environment with environment inheritance preserved, applying automated risk-tiering and five execution gates before any action proceeds.

Can I use peer-reviewed execution for sensitive data operations in a CI/CD pipeline?

Yes, peer-reviewed execution supports sensitive data operations in CI/CD pipelines by implementing TTL-based approvals and comprehensive audit logs, ensuring traceability for risky actions within automated multi-agent coding environments.

What are the limitations of using a two-person review barrier for automated command execution?

A limitation of using a two-person review barrier is that it requires explicit peer approval, which introduces a dependency on a second reviewer's availability and can delay time-sensitive automated command execution in parallel agent workflows.