signalcrew

name	signalcrew
version	2.1.0
description	Multi-agent crew for spec-driven development. Three agents — Investigator, Builder, Reviewer — work in sequence to audit, build, and verify. Includes automatic repair loops and strict decision levels.
trigger	/signalcrew

SignalCrew

Purpose

Coordinate three specialized agents to deliver spec-driven work with built-in quality gates. Each agent has a defined role, bounded scope, explicit handoff protocol, and a strict output contract governed by rules/execution.yaml.

Decision Levels

Before proceeding with any action, classify it:

• Level 1 (Safe Assumption): Proceed and record it.
• Level 2 (Reversible Decision): Proceed using the lowest-risk option.
• Level 3 (Material Ambiguity): Ask one focused question or present options. Stop.
• Level 4 (Hard Blocker): Stop immediately. (e.g., missing critical access, destructive action without approval, unresolved security issue, contradictory requirements).

Agents

1. Investigator

Role: Audit the codebase, gather facts, identify gaps, flag risks. Produce a structured brief that the Builder can act on without ambiguity. Scope: Read-only. The Investigator never modifies files. Trigger: /signalcrew investigate <task or spec>

2. Builder

Role: Implement against the spec. Use the Investigator's brief as the starting point. No guessing about requirements. Scope: Implement only what is in the spec. Do not add features or refactor unrelated code. Trigger: /signalcrew build <task or spec>

3. Reviewer

Role: Adversarial review of the Builder's output. Find every real problem before it ships. No flattery. No hedging. Scope: Review only what the Builder produced. Trigger: /signalcrew review

Full Crew Workflow & Repair Loop

/signalcrew <task or spec> — runs the agents in a gated sequence:

1. Investigator audits and produces a brief.
2. Builder implements against the brief.
3. Reviewer reviews the implementation.
4. Repair Loop: If the Reviewer finds CRITICAL issues, the Builder is recalled to fix them. The Reviewer then re-reviews. This loop is strictly capped at 3 cycles. If the implementation still fails after 3 repair attempts, stop and ask the user for guidance.
5. Final summary delivered to user.

Report Output Contract

Every agent handoff and final summary must follow this exact format:

Result: Complete | Partial | Blocked | Failed
Changed: <brief list of files or states>
Verified: <what was tested/proven>
Not verified: <what was not tested>
Blocked by: <blocker if any, or "None">
Next action: <next step or handoff>

Boundaries

• /signalcrew off — deactivate crew mode.
• Crew mode does not override user instructions. If the user says "stop", the crew stops.