Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .changeset/claude-polish.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,10 @@
---
"@bradygaster/squad-sdk": patch
"@bradygaster/squad-cli": patch
---

Claude Code follow-ups from the end-to-end test:

- New `squad client sync` refreshes the configured hosts' files. Init Mode now runs it after writing `routing.md`, so Claude Code member subagent descriptions say what each member owns instead of repeating the role (#2456).
- `squad_state_health` and `squad health --json` add `resolvedTeamRoot` (the directory that contains `.squad`) and `resolvedSquadDir` (the squad directory itself). `resolvedTeamDir` keeps its value, the team root, for existing consumers (#2455).
- The Claude coordinator no longer asks Scribe for session or orchestration logs, which Scribe's charter and the Copilot coordinator retired (#2454).
8 changes: 8 additions & 0 deletions .squad-templates/skills/cli-wiring/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,11 @@
---
name: "cli-wiring"
description: "Checklist for wiring a new Squad CLI command: route it in cli-entry.ts, add help text, and test that it is reachable"
domain: "cli"
confidence: "high"
source: "team-decision"
---

# Skill: CLI Command Wiring

**Bug class:** Commands implemented in `packages/squad-cli/src/cli/commands/` but never routed in `cli-entry.ts`.
Expand Down
8 changes: 8 additions & 0 deletions .squad-templates/skills/retro-enforcement/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,11 @@
---
name: "retro-enforcement"
description: "Keep retrospectives on schedule and track their action items as GitHub Issues, not markdown checklists"
domain: "process"
confidence: "high"
source: "team-decision"
---

# Skill: Retro Enforcement

## Purpose
Expand Down
3 changes: 3 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,9 @@ Claude Code is the first host after GitHub Copilot where Squad uses the host's o

- The Claude coordinator names Claude Code's `Agent` subagent tool (formerly `Task`). The Claude Code spec, docs and host feature matrix now match the code, and host-projection regression guards keep them that way (#2440, #2445).
- Every generated Claude Markdown file states its projection version. Files from earlier projections are still recognised as Squad's and upgraded in place, and rolling back the `CLAUDE.md`, `AGENTS.md` and `GEMINI.md` blocks restores the original bytes exactly (#2450).
- New `squad client sync` refreshes the configured hosts' files without a full upgrade. Init Mode runs it after writing `routing.md`, so each Claude Code member subagent's description names what the member owns instead of repeating its role (#2456).
- `squad_state_health` and `squad health --json` add `resolvedTeamRoot` (the directory that contains `.squad`) and `resolvedSquadDir` (the squad directory itself). `resolvedTeamDir` keeps its value, the team root, for existing consumers (#2455).
- The Claude coordinator no longer asks Scribe for session or orchestration logs, matching Scribe's charter and the Copilot coordinator (#2454).
- Copilot output, `.github/agents/squad.agent.md` and the projections for other hosts are unchanged, apart from the portable `squad_state` launch command below, which every host gets.

#### Fixed
Expand Down
2 changes: 1 addition & 1 deletion docs/src/content/docs/reference/cli.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ prerequisites, all supported methods, and update commands.
| `squad state-mcp [--experimental-backend]` | Run the `squad_state` stdio MCP server; pass `--experimental-backend` (or `SQUAD_EXPERIMENTAL_BACKEND=1`) to also expose the 11 experimental `squad_backend_*` conversation tools (transcript/event-log only until a harness is registered) | Yes |
| `squad --version` | Print installed version | No |

`squad health --json` preserves the `squad-health/v1` schema and includes `metadata` fields for `cliVersion`, `sdkVersion`, `stateBackend`, `resolvedTeamDir`, `bridgeVersion`, and `launchMode`. Human-readable output is unchanged.
`squad health --json` preserves the `squad-health/v1` schema and includes `metadata` fields for `cliVersion`, `sdkVersion`, `stateBackend`, `resolvedTeamRoot` (the directory that contains `.squad`), `resolvedSquadDir` (the squad directory itself), `bridgeVersion`, and `launchMode`. `resolvedTeamDir` is kept for existing consumers and holds the same value as `resolvedTeamRoot`; despite its name, it is not the squad directory. Human-readable output is unchanged.

The `squad_state_health` MCP tool includes the same fields in a JSON `Health metadata` line while retaining its existing state and storage lines.

Expand Down
2 changes: 2 additions & 0 deletions docs/src/content/docs/scenarios/client-compatibility.md
Original file line number Diff line number Diff line change
Expand Up @@ -200,6 +200,8 @@ Squad runs on VS Code with **conditional support**. Key differences from CLI:
- `.gitignore` — `.claude/worktrees/` under a `# squad:claude` comment
- `.claude/settings.json` — Squad's governance hooks, only if you opt in (see below). Your other settings and hooks are kept.

`squad init --client claude` also writes the GitHub Copilot files: `.github/agents/squad.agent.md`, `.github/skills/`, `.copilot/mcp-config.json`, the Squad workflows under `.github/workflows/` and `.vscode/settings.json`. This is intended. GitHub Copilot is the base host, and `.github/agents/squad.agent.md` is the canonical coordinator that the other hosts' coordinators are checked against ([ADR-003](https://github.com/github/squad/blob/dev/docs/specification/adr-003-host-neutral-canonical-coordinator.md) proposes a host-neutral source instead). Skip the workflows with `--no-workflows` and the VS Code setting with `--no-vscode-default`.

### Starting a session

```bash
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,12 @@ For an existing repo:
npx squad upgrade --client copilot,claude,cursor
```

To refresh the configured hosts' files without a full upgrade, for example after you edit `.squad/routing.md` (Claude Code member subagent descriptions are built from it):

```bash
npx squad client sync
```

## What each adapter generates

| Client (`ClientId`) | Generated files |
Expand Down
2 changes: 1 addition & 1 deletion packages/squad-cli/src/cli-entry.ts
Original file line number Diff line number Diff line change
Expand Up @@ -147,21 +147,21 @@
// "Unknown command: version" reports may be shell-specific (e.g. alias/wrapper
// prepending flags so args[0] is no longer 'version'). No intercepting router found.
if (cmd === '--version' || cmd === '-v' || cmd === 'version') {
console.log(VERSION);

Check warning on line 150 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / Verify exact SHA and build evidence

Unexpected console statement. Only these console methods are allowed: warn, error

Check warning on line 150 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / test

Unexpected console statement. Only these console methods are allowed: warn, error
return;
}

// --help / -h / help
if (cmd === '--help' || cmd === '-h' || cmd === 'help') {
console.log(`\n${BOLD}squad${RESET} v${VERSION} — Add an AI agent team to any project\n`);

Check warning on line 156 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / Verify exact SHA and build evidence

Unexpected console statement. Only these console methods are allowed: warn, error

Check warning on line 156 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / test

Unexpected console statement. Only these console methods are allowed: warn, error
console.log(`Usage: squad [command] [options]\n`);

Check warning on line 157 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / Verify exact SHA and build evidence

Unexpected console statement. Only these console methods are allowed: warn, error

Check warning on line 157 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / test

Unexpected console statement. Only these console methods are allowed: warn, error
console.log(`Commands:`);

Check warning on line 158 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / Verify exact SHA and build evidence

Unexpected console statement. Only these console methods are allowed: warn, error

Check warning on line 158 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / test

Unexpected console statement. Only these console methods are allowed: warn, error
console.log(` ${BOLD}(default)${RESET} Launch interactive shell (no args)`);

Check warning on line 159 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / Verify exact SHA and build evidence

Unexpected console statement. Only these console methods are allowed: warn, error

Check warning on line 159 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / test

Unexpected console statement. Only these console methods are allowed: warn, error
console.log(` ${BOLD}init${RESET} Initialize Squad (markdown-only, default)`);

Check warning on line 160 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / Verify exact SHA and build evidence

Unexpected console statement. Only these console methods are allowed: warn, error

Check warning on line 160 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / test

Unexpected console statement. Only these console methods are allowed: warn, error
console.log(` Flags: --sdk (SDK builder syntax)`);

Check warning on line 161 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / Verify exact SHA and build evidence

Unexpected console statement. Only these console methods are allowed: warn, error

Check warning on line 161 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / test

Unexpected console statement. Only these console methods are allowed: warn, error
console.log(` --roles (use base roles)`);

Check warning on line 162 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / Verify exact SHA and build evidence

Unexpected console statement. Only these console methods are allowed: warn, error

Check warning on line 162 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / test

Unexpected console statement. Only these console methods are allowed: warn, error
console.log(` --no-workflows (skip CI setup)`);

Check warning on line 163 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / Verify exact SHA and build evidence

Unexpected console statement. Only these console methods are allowed: warn, error

Check warning on line 163 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / test

Unexpected console statement. Only these console methods are allowed: warn, error
console.log(` --no-vscode-default (skip .vscode/settings.json update)`);

Check warning on line 164 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / Verify exact SHA and build evidence

Unexpected console statement. Only these console methods are allowed: warn, error

Check warning on line 164 in packages/squad-cli/src/cli-entry.ts

View workflow job for this annotation

GitHub Actions / test

Unexpected console statement. Only these console methods are allowed: warn, error
console.log(` --preset <name> (apply a preset after init)`);
console.log(` --state-backend <type> (local|orphan|two-layer)`);
console.log(` --client <list> (hosts, or "all"); --claude-plugin`);
Expand All @@ -181,7 +181,7 @@
console.log(` --insider (with --self: force the insider channel)`);
console.log(` --force (with --self: allow a downgrade)`);
console.log(` ${BOLD}client${RESET} Manage client host projections (Copilot, Claude, Kiro, …)`);
console.log(` Usage: client list [--json] | client add <list> [--dry-run]`);
console.log(` Usage: client list [--json] | client add <list> | client sync`);
console.log(` ${BOLD}roster${RESET} Explicitly opt optional built-ins into team.md`);
console.log(` Usage: roster add|remove <rai|fact-checker|all> [--dry-run]`);
console.log(` ${BOLD}update-check${RESET} Report cached CLI update status (for tooling/CI)`);
Expand Down
26 changes: 25 additions & 1 deletion packages/squad-cli/src/cli/commands/client.ts
Original file line number Diff line number Diff line change
Expand Up @@ -156,6 +156,30 @@ export async function runClientCommand(dest: string, args: string[]): Promise<nu
}
}

console.error(`❌ Unknown client subcommand: ${sub}\n Usage: squad client list [--json] | squad client add <list> [--dry-run]`);
if (sub === 'sync') {
// Re-project the configured hosts, e.g. after routing.md changes (#2456): Claude member
// subagent descriptions are built from it. Only Squad-managed files are rewritten.
try {
const squadDir = detectSquadDir(dest).path;
const synced = await syncClients(dest, squadDir, { dryRun, warn: (m) => console.warn(m) });
Comment on lines +163 to +164
if (synced.clients.length === 0) {
console.log('No client hosts configured in .squad/config.json; nothing to sync. Add one with: squad client add <list>');
return 0;
}
if (dryRun) {
console.log(`Would refresh client host files for: ${synced.clients.join(', ')} (nothing written: --dry-run)`);
return 0;
}
reportClientResults(synced.results);
const failed = synced.results.some((r) => r.action === 'error');
console.log(`${failed ? '⚠' : `${GREEN}✓${RESET}`} clients synced: ${synced.clients.join(', ')}`);
return failed ? 1 : 0;
} catch (err) {
console.error(`❌ ${err instanceof Error ? err.message : String(err)}`);
return 1;
}
}

console.error(`❌ Unknown client subcommand: ${sub}\n Usage: squad client list [--json] | squad client add <list> [--dry-run] | squad client sync [--dry-run]`);
return 1;
}
7 changes: 7 additions & 0 deletions packages/squad-cli/src/cli/commands/health.ts
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,12 @@ export interface HealthReport {
cliVersion: string;
sdkVersion: string;
stateBackend: string;
/** The team root (the directory that contains `.squad`), despite its name; kept for v1 consumers (#2455). */
resolvedTeamDir: string | null;
/** The team root: the directory that contains the squad directory. */
resolvedTeamRoot: string | null;
/** The squad directory itself (`.squad`, or a flat externalized team directory). */
resolvedSquadDir: string | null;
bridgeVersion: string;
launchMode: 'cli';
};
Expand Down Expand Up @@ -642,6 +647,8 @@ function healthMetadata(
sdkVersion: SDK_VERSION,
stateBackend,
resolvedTeamDir: stateDir ? resolvedTeamDirectory(stateDir) : null,
resolvedTeamRoot: stateDir ? resolvedTeamDirectory(stateDir) : null,
resolvedSquadDir: stateDir ? path.resolve(stateDir) : null,
bridgeVersion: cliVersion,
launchMode: 'cli',
};
Expand Down
8 changes: 5 additions & 3 deletions packages/squad-cli/src/cli/core/command-help.ts
Original file line number Diff line number Diff line change
Expand Up @@ -73,14 +73,16 @@ const COMMAND_HELP: Record<string, HelpPrinter> = {
client: (version) => {
header('client', version, 'Manage client host projections');
console.log(`Usage: squad client list [--json]`);
console.log(` squad client add <list> [--dry-run]\n`);
console.log(` squad client add <list> [--dry-run]`);
console.log(` squad client sync [--dry-run]\n`);
console.log(`Lists the hosts configured in .squad/config.json (clients[]) and whether their`);
console.log(`projected files exist. An empty clients[] means only the default GitHub Copilot`);
console.log(`host (.github/agents/squad.agent.md + .mcp.json) is projected.\n`);
console.log(`host (.github/agents/squad.agent.md + .mcp.json) is projected. sync refreshes the`);
console.log(`configured hosts' files, e.g. Claude member subagents after routing.md changes.\n`);
console.log(`Hosts: copilot, claude, kiro, opencode, cursor, codex, antigravity, or "all".\n`);
console.log(`Options:`);
console.log(` ${BOLD}--json${RESET} Emit structured JSON instead of text`);
console.log(` ${BOLD}--dry-run${RESET} With add: show what would be projected, write nothing\n`);
console.log(` ${BOLD}--dry-run${RESET} With add or sync: show what would be projected, write nothing\n`);
},

roster: (version) => {
Expand Down
8 changes: 8 additions & 0 deletions packages/squad-cli/templates/skills/cli-wiring/SKILL.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,11 @@
---
name: "cli-wiring"
description: "Checklist for wiring a new Squad CLI command: route it in cli-entry.ts, add help text, and test that it is reachable"
domain: "cli"
confidence: "high"
source: "team-decision"
---

# Skill: CLI Command Wiring

**Bug class:** Commands implemented in `packages/squad-cli/src/cli/commands/` but never routed in `cli-entry.ts`.
Expand Down
Original file line number Diff line number Diff line change
@@ -1,3 +1,11 @@
---
name: "retro-enforcement"
description: "Keep retrospectives on schedule and track their action items as GitHub Issues, not markdown checklists"
domain: "process"
confidence: "high"
source: "team-decision"
---

# Skill: Retro Enforcement

## Purpose
Expand Down
4 changes: 2 additions & 2 deletions packages/squad-sdk/src/client/adapters/coordinator.ts
Original file line number Diff line number Diff line change
Expand Up @@ -112,7 +112,7 @@ You are the Squad coordinator. You route work to a team of specialists and keep
0. **Init Mode (only when there is truly no team).** Decide this with \`squad_state_read\` of \`team.md\` (or \`squad_state_list\`), NEVER with glob/grep/search tools: many hosts' glob/grep skip dot-directories like \`${S}/\` and will wrongly report "no matches". If \`team.md\` is readable and lists members, a team exists: NEVER overwrite or re-cast it, or its charters, decisions, history or casting records; use it. Only if \`team.md\` does not exist or has an empty roster:
- **Phase 1 (propose).** Infer the project's purpose from the request and repository (ask only if it is genuinely unknowable AND the session is interactive). Propose 3-5 specialists with a thematic universe, names and roles (a Lead, domain implementers, a Tester; Scribe, Ralph, Rai and Fact Checker are always-on built-ins).
- **Auto-confirm (default).** Do NOT stop to ask questions in Init Mode. The user's request is the confirmation: pick sensible defaults for anything unspecified (stack, scope, universe), record those assumptions under \`Project Context\` in \`team.md\`, and continue to Phase 2 in the SAME turn. This is mandatory when the user said to proceed / confirm / go, or the host runs headless (print / exec / no question tool). Only an interactive session with a genuinely unknowable purpose may ask, and then at most ONE short question. Never end the turn with only a proposal or questions.
- **Phase 2 (create).** If you can run shell commands, add EVERY member with the CLI, one call each: \`npx squad cast --name <Name> --role "<Role>"\` (it writes the charter, history, the \`team.md\` roster row, \`routing\` hooks and the casting registry/history pair correctly; the built-ins scribe, ralph, rai and fact-checker already exist after \`squad init\`). Then write/adjust \`${S}/routing.md\` as an ordinary file. If \`squad cast --name\` is not recognised (an older \`squad\` build that only lists the cast; \`npx\` may fetch an old published version, so prefer the \`squad\` on PATH), tell the user to upgrade the squad CLI instead of hand-writing the team. NEVER hand-write or edit anything under \`${S}/casting/\` (\`registry.json\`, \`history.json\`, \`registry-history.commit.json\` are a checksummed pair: manual edits make \`squad upgrade\` fail with a registry error). If you cannot run shell commands, write \`team.md\` (a markdown table with \`Name\`, \`Role\`, \`Charter\`, \`Status\` columns; the Coordinator row stays separate), \`${S}/agents/<lowercase-name>/charter.md\` and \`history.md\` as ordinary files, leave \`${S}/casting/\` untouched and tell the user to run \`squad cast --name <Name> --role "<Role>"\` for each member to register them.
- **Phase 2 (create).** If you can run shell commands, add EVERY member with the CLI, one call each: \`npx squad cast --name <Name> --role "<Role>"\` (it writes the charter, history, the \`team.md\` roster row, \`routing\` hooks and the casting registry/history pair correctly; the built-ins scribe, ralph, rai and fact-checker already exist after \`squad init\`). Then write/adjust \`${S}/routing.md\` as an ordinary file, and once routing is written run \`squad client sync\` so host files built from it (Claude Code member subagent descriptions) pick up who owns what; it rewrites only Squad-managed files. If \`squad cast --name\` is not recognised (an older \`squad\` build that only lists the cast; \`npx\` may fetch an old published version, so prefer the \`squad\` on PATH), tell the user to upgrade the squad CLI instead of hand-writing the team. NEVER hand-write or edit anything under \`${S}/casting/\` (\`registry.json\`, \`history.json\`, \`registry-history.commit.json\` are a checksummed pair: manual edits make \`squad upgrade\` fail with a registry error). If you cannot run shell commands, write \`team.md\` (a markdown table with \`Name\`, \`Role\`, \`Charter\`, \`Status\` columns; the Coordinator row stays separate), \`${S}/agents/<lowercase-name>/charter.md\` and \`history.md\` as ordinary files, leave \`${S}/casting/\` untouched and tell the user to run \`squad cast --name <Name> --role "<Role>"\` for each member to register them.
- **After casting**, STOP and report the roster unless the user's request also asked for work (setting up the team is not a request to build anything).
- **Scratch space.** Use \`${S}/scratch/\` (inside the workspace) for temporary files; never write outside the workspace directory (hosts reject external-directory access).
1. **Load team context first.** Read \`${S}/team.md\` (roster), \`${S}/routing.md\` (who owns what), \`${S}/decisions.md\` and the decisions inbox before routing anything. Cache them for the session; re-read only when a state change was announced.
Expand All @@ -128,7 +128,7 @@ You are the Squad coordinator. You route work to a team of specialists and keep
## Behavioral contract (same as Copilot)

10. **Response Mode Selection.** Pick the lightest mode that is correct, biasing upward when unsure: **Direct** (you answer from known facts, no spawn: status, roster, "who owns X", trivial questions); **Lightweight** (one specialist, minimal context: typo, small read-only lookup); **Standard** (one or more specialists with full charter/decision context: normal feature/bug work); **Full** (multi-agent fan-out plus reviewer gate and Scribe: cross-cutting or risky work). Acknowledge immediately before spawning: one line naming who you are launching and why, then spawn.
11. **Scribe spawn protocol and drop-box pattern.** Agents never write \`${S}/decisions.md\` directly: decisions go to \`${S}/decisions/inbox/\` (via \`squad_decide\`). After a substantive batch of work (or when the inbox is non-empty at session end), spawn **Scribe** (background/last) with its charter to: run \`squad_state_health\`; list the inbox; merge each entry into \`decisions.md\` (demote headings beneath a dated \`###\` entry, de-duplicate), re-read to verify, then delete only processed inbox entries; append a session log to \`${S}/log/\` and an entry to \`${S}/orchestration-log/\`; archive old decisions only through the state tools/\`squad nap\`, never by hand-deleting history. Scribe never commits mutable state. If a required state tool is unavailable, report it; do not fall back to unsafe direct writes.
11. **Scribe spawn protocol and drop-box pattern.** Agents never write \`${S}/decisions.md\` directly: decisions go to \`${S}/decisions/inbox/\` (via \`squad_decide\`). After a substantive batch of work (or when the inbox is non-empty at session end), spawn **Scribe** (background/last) with its charter to: run \`squad_state_health\`; list the inbox; merge each entry into \`decisions.md\` (demote headings beneath a dated \`###\` entry, de-duplicate), re-read to verify, then delete only processed inbox entries; archive old decisions only through the state tools/\`squad nap\`, never by hand-deleting history. Scribe never commits mutable state, and neither Scribe nor you writes session logs or orchestration logs (retired; Scribe's charter rules them out). If a required state tool is unavailable, report it; do not fall back to unsafe direct writes.
12. **Reviewer rejection protocol and strict lockout.** Work that needs review goes to a reviewer (Lead, Tester or Rai as appropriate) before it is declared done. A reviewer returns APPROVE or REJECT with reasons. On REJECT the original author is **locked out** from revising that artifact: reassign the revision to a different member (or escalate to the Lead/architect); a locked-out author may not self-revise or re-submit. Re-review is required after the revision. If reviewers and authors deadlock, escalate to the user with both positions. Record verdicts via \`squad_decide\`.
13. **Rai (RAI Reviewer).** Rai performs Responsible-AI review: targeted ("RAI check", "is this safe to ship?"), pre-ship for user-facing artifacts, and pre-merge. Verdicts: 🟢 Green (proceed), 🟡 Yellow (advisory, proceed with recommendations attached), 🔴 Red (blocks shipping: triggers the reviewer rejection protocol with Rai naming a fix agent and re-reviewing). Rai runs in the background by default (non-blocking) and becomes a blocking gate only on Red; findings state WHAT is wrong, WHY it matters and HOW to fix it. Policy and audit trail: \`${S}/rai/policy.md\`, \`${S}/rai/audit-trail.md\` (append via state tools).
14. **Fact Checker (verification and devil's advocate).** Spawn the Fact Checker to verify claims, URLs, packages, APIs and external references, rating each ✅ verified, ⚠️ partially verified / caveat, ❌ contradicted, 🔍 unverifiable/needs a source; findings are advisory and never implement or decide. On request ("challenge this plan", "devil's advocate") it steelmans the plan, lists assumptions, runs a pre-mortem, proposes alternatives and states the risk being accepted. Audit trail: \`${S}/fact-checker/audit-trail.md\`.
Expand Down
Loading
Loading