Slash Command83 repo starsupdated 9d ago

triage

The triage slash command launches a diagnostic agent team to identify the root cause and impact scope of an issue without making any code changes, commits, or pull requests. Use this when you need a confidence-rated diagnosis of a bug, performance problem, or system behavior and want multiple specialized perspectives on the likely cause and blast radius before deciding whether to fix it.

View source Repository: swarms

Install in Claude Code

Copy

mkdir -p ~/.claude/commands && curl -fsSL https://raw.githubusercontent.com/DheerG/swarms/HEAD/commands/triage.md -o ~/.claude/commands/triage.md

Then start a new Claude Code session; the slash command loads automatically.

Definition

triage.md

# /swarm:triage

Read `${CLAUDE_PLUGIN_ROOT}/commands/launch.md` for Step 0 (pre-flight), Step 1 (hard rules), and Step 8 (launch). This command replaces Steps 2–7.

**No lead research unless enabled.** Unless the user explicitly enables lead research, do not read codebase files, spawn subagents, or perform research. Delegate all evidence-gathering to teammates.

**Triage changes nothing.** This mode diagnoses — it does not branch, commit, edit, or open a PR. The deliverable is a confidence-rated diagnosis presented in-session.

## Settings

- **Mode:** Triage
- **Outcomes question:** "What do you want the team to diagnose? (Describe what you're seeing — the symptom, where it shows up, and any context. The team will identify the likely cause and the blast radius of fixing it, without making any change.)"
- **Defaults:** suggest-members (Triage mode), tier picked at setup (Ultra recommended), no lead research

## User-Provided Context

$ARGUMENTS

## Workflow

1. **Setup.** AskUserQuestion — "How would you like to set up the team?" Options: "Defaults — Ultra (Recommended)" (auto-configure mode/team/research; full team on the stronger model — reliable rule-following) / "Defaults — Balanced" (same auto-config; cheaper model for members — lower cost, less reliable rule-following) / "Configure each step" (choose mode, team, tier, research individually).
2. **Outcomes.** If User-Provided Context is non-empty, use as outcomes. Otherwise ask the outcomes question (plain text, not AskUserQuestion). Do NOT echo the outcomes back verbatim — run the outcome reflection instead: You MUST use the **Skill** tool to invoke `swarm:reflect-outcome` with the user's exact words as `args`, and do not author its wording yourself. If it returns `NO FORK` (the common case), show nothing — no echo, no confirmation beat — and carry the outcome forward to the Step 7 team-plan summary, where it is restated (that is where the user sees their words carried forward). If it returns a ready-to-render fork, present it with AskUserQuestion exactly as returned (transport it, do not reword the question or labels) and resolve the user's pick per the skill — Option A keeps their wording, Option B re-authors into a new verbatim. Store no separate supplement. The user's verbatim words are still captured for the Step 8 briefs (launch.md verbatim-capture rule); the user can still adjust at Step 7.
3. **Team configuration.** Defaults path (either Defaults option): apply the defaults above with the tier set to the option picked (Ultra or Balanced), and immediately proceed to step 4 in the same response — do not pause for user input. Configure path: follow launch.md Steps 4–6, then step 4.
4. **Confirmation.** Follow launch.md Step 7. Mode is Triage.
5. **Launch.** Follow launch.md Step 8.