Five rooms. Two doors in.

Delivery isn't one page — it's the whole hallway you've already walked: Architecture, Agents, Skills, Commands, and Build. Every feature enters through discovery. A confirmed bug gets a second, faster door: the GitHub issue is already the spec, so three stages never run at all.

01 / The five rooms

Delivery was already built. This just finds the door.

Nothing on this page replaces any of these five — each one is a full lesson on its own. This is the map, not the territory.

Architecture

The system is the handoffs.

Explicit, append-only artifacts instead of hidden conversation state.

Agents

A specialist with a hard edge.

Bounded judgment, one output, an explicit stopping point.

Skills

Teach it once. Reuse the judgment.

Reusable policy attached to a role, or loaded when a trigger matches.

Commands

One entrance. One clear route.

A routing contract that transfers control — not a miniature agent.

Build

Build the control plane before the team.

Prove one complete retry before adding roles.

02 / What a bug skips

The issue is the spec. Nothing else has to write one.

Bug Fix Mode isn't a shortcut through rigor — it's a shortcut through the three stages whose whole job is producing a spec. A confirmed bug already has one: the GitHub issue itself.

Skipped

Discovery, Architecture, Design

Each one exists to turn ambiguous intent into a written contract. A bug report that's already been triaged and labeled bug is that contract — writing a second one would be redundant, not more rigorous.

Unchanged

Engineer → 4 reviews → Gate → PR

Same engineer contract, the same four parallel reviewers, the same combined-verdict gate, the same never-auto-merge rule. A bug fix is not "less reviewed" — it's differently sourced.

Numbering, not meaning, changes

Bug Fix Mode's stages are labeled B1–B10 instead of 1–9 specifically so a bug's sequence numbers never collide with a feature's — docs/bugfixes/{N}-{slug}/ is a separate directory tree from docs/briefs/{NNN}-{feature}/ entirely.

03 / Who decides it's a bug

Triage recommends. It never runs the fix itself.

Deterministic

Fixed by the command

/fix requires a bare issue number — no guessing which bug
Confirms the bug label is present before doing anything else
Stops and asks if the label is missing, rather than assuming

Probabilistic

Judged by bug-triage

Whether a reported bug actually reproduces
Severity and whether it hits a named persona's ICP
Direct fix, escalate to /feature, or reclassify entirely

Recommend, never route

bug-triage ranks the open bug queue and recommends a route — "Fix Now," "Fix Soon," "Escalate to /feature," or a handful of close/reclassify outcomes. It never invokes /fix itself; running the fix is a separate, human-initiated command, the same boundary every other analyst on this site respects.

Read the source documentation