Builder Garage

Two ways into the Garage.

Adopt the framework or hand-place individual artifacts. Both paths use the canonical skill contracts and configuration rules.

PATH A

Use the framework

Install the CLI from the verified source revision:

macOS and Linux
git clone https://github.com/bdonaldharris/builder-garage.git
cd builder-garage
git checkout db2fcaca6e315cd2a2732a963b6253edd831926e
./install.sh
garage version

Requires Go 1.27.4 to build. The source installer supports macOS and Linux and installs to ~/.local/bin without changing PATH. On Windows, build by hand. If ~/.local/bin is not on PATH, follow the installer's instructions before continuing.

Windows and manual builds →

Configure your project

Run these from your project's root. In a terminal, garage init guides you through human authorities, policies, manuals, and skill targets, then asks for confirmation.

from your project root
garage init
garage config validate
garage skills install
garage skills verify

Declare at least one supported user-scope skill target before installing. The installer builds the CLI; garage skills install separately installs the complete embedded canonical skill set and adopted manuals. It never invokes an agent or advances a workflow.

PATH B

Use individual artifacts

Download a skill ZIP or manual Markdown file from the Library. Preserve each skill's directory structure and follow your harness's skill-location rules.

HarnessCLI-managed user directory
Claude Code~/.claude/skills
Codex~/.codex/skills
Copilot CLI~/.copilot/skills

These are the CLI's default user-scope paths. It also honors CLAUDE_CONFIG_DIR, CODEX_HOME, and COPILOT_HOME. Project-scope installs are not supported by the CLI. Harness path behavior was confirmed on macOS; Linux and Windows harness behavior remains unconfirmed.

Browse the Library

Hand-placed skills are unmanaged, not standalone executables. Canonical skills use garage config validate when resolving project choices, so those steps still require the CLI on PATH and valid configuration. Manuals apply only when the project adopts them. Read the configuration contract before use.

What exists today

Available: source installation on macOS and Linux; manual builds including Windows; 6 reusable engineering skills; 3 technology manuals (provisional); the operating model, review contract, governance, and contribution guides.

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 and pull-request workflow status through authenticated gh; and reports its version.

Not implemented: workflow execution or agent orchestration, agent configuration, AI-provider connections, plugin loading, remote services, libraries, adapters, SDKs, or release automation. Version tags exist, but published binary releases and installation packages do not.