Builder Garage

A workflow with boundaries.

Builder Garage defines responsibilities, evidence, and handoffs. The CLI supports the work; it does not orchestrate it.

  1. 01

    Discover

    Understand the system before changing it.

  2. 02

    Assess readiness

    Resolve material uncertainty deliberately.

  3. 03

    Implement

    Keep work scoped to the evidence.

  4. 04

    Inspect

    Independent review tests the real artifact.

  5. 05

    Ship

    Human authority remains with the maintainer.

The five-step flow is an overview, not a mandatory checklist. Discovery applicability is configured by the project; a separate readiness pass depends on the change's uncertainty and complexity.

Five conceptual shop areas

Workbench holds procedures; Crew defines who acts; Inspection defines independent verification; Shipping covers integration and promotion; Manuals provide technology guidance. These are responsibilities, not five implemented runtime products.

Roles and workflow positions

The Technician roles are discovery, readiness, planner, implementer, and reviewer. Human authorities make workflow, change-acceptance, and product-intent decisions. Agent #1 and Agent #2 are workflow positions, not interchangeable personas.

Agent #1 — Implementation

The implementer owns scoped implementation, correction, validation, and integration-PR finalization. It stops at an independent-review handoff.

Agent #2 — Independent review

A separately invoked reviewer inspects the complete artifact and records its disposition on the governing issue or PR. It never implements or corrects that artifact.

How people and agents fill the roles →

The review contract

  1. Were the issue's acceptance criteria met?
  2. Did the implementation introduce a new bug or regression?
  3. Does the implemented behavior work?

Yes → No → Yes means independent approval, not authorization to merge. The originating issue's implementation review remains authoritative; a supplemental PR review is required only when a trigger applies. Automated reviewers are optional input, never a substitute for Agent #2.

Required checks, deployment-requirement visibility, configured release conditions, human change acceptance, and product-intent acceptance still govern merge. Where practical, user-facing changes are inspected by the human product-intent acceptor.

See the complete gate map →

Current CLI capabilities

The CLI initializes and upgrades project configuration; validates, shows, and changes settings; records private local workflow events; installs and verifies canonical skills and adopted manuals; reads issue or pull-request workflow status through gh; and reports its version. It does not execute workflows, configure agents, connect AI providers, load plugins, or provide remote services.

Local workflow history is a private annotation, not review evidence. GitHub issue and PR records are authoritative. garage status reads GitHub once through authenticated gh; it never polls, assigns agents, or advances work.