Let the orcs do the work.

One command from “I want X” to a merged PR.

Run each step yourself, or let /orc:flow drive all of them with a gate at every decision. Every phase writes to .orc/, so an interrupted session picks up with /orc:resume.

.orc/feat-PROJ-142/files/
├── plan.md            4 slices · est 288 LOC
├── slices.json        pending ×4
└── decisions.json     type=feature scope=medium

Watch the work happen inside Claude Code.

The orc mod draws the flow into the app itself: a progress band above the prompt, a live row per agent, a docked cockpit with every file touched and the blast radius, and alerts that stop you before anything risky. Rich graphics on Claude Desktop, plain text in the terminal, same data underneath.

Claude DesktopTerminal

ChatCode

/orc:flow add CSV export to the reports page --jira PROJ-142

Plan approved: four slices, 288 lines. Slices 1 and 2 are committed. Slices 3 and 4 touch separate files, so two implementers run them in parallel.

orc-state slice set 3 --status red · slices 2/4

Agents

CockpitReplay

Reply to Claude…

orc flow · implement · ⏎ to steer the implementers

orc · guidedOpus 5.5 · high

AbovePrompt · CI watcher

DiagnoseDismiss

A linked PR turns red; the band names the failing checks. Diagnose hands it to /orc:ci. It never pushes or posts on its own.

AbovePrompt · destructive git

Before git clean, reset --hard or a force-push, the band shows exactly what would be lost, next to the confirm prompt.

AbovePrompt · sentinel

An edit outside the slice's declared files, or a slice outgrowing its line budget, raises a heads-up while there is still time to steer.

AbovePrompt · cache

A long wait on an agent is about to let the prompt cache expire. The band says what the re-write will cost before you step away.

AbovePrompt · retro

SaveSkip

A correction you made twice becomes a proposed rule. Save it, edit it, or skip it; /orc:retro picks up the rest.

AskUserQuestion · gate badge

Post · outwardPlan · inward

Gate badges

Every gate carries a chip for its class. Outward gates, which post to GitHub or a tracker, always ask, whatever the autopilot level.

Graphics above are rendered by orc's mod code (orc/hooks/mod/*/svg.ts) with sample data; the window around them is illustrative. Needs Claude Code 2.1.287 or later with mod_enabled on (the default). Turn the mod off and every guardrail still runs from the bash hooks.

Say what happened. orc picks the command.

Every situation a working day throws at you has one entry point. Type the situation, or ask /orc:map inside Claude Code.

Rules the model cannot talk its way past.

Every guardrail is a short shell script Claude Code runs as a real hook. Read them in five minutes, diff them by tag, and trust what you read.

$ git commit -m "fix: retry"   # jq missing
ask  orc guards need jq and it is not
     on PATH. Failing closed.
     Install it (orc doctor --fix) or
     confirm this command deliberately.

Written like a maintenance manual, because an agent reads it like one.

orc's commands follow the rules aircraft manuals use so a stranger performs a procedure exactly: controlled vocabulary, short verb-first steps, warnings before the step, and small modules loaded one phase at a time. A lint enforces it on every PR.