/build

Take a plan from /launch and ship it. One builder per user story. Runs /verify. Opens PRs. Gates prod on a human. Refuses auth, schema, security, and tenant work. Two modes — full and degrade-with-note.

Copy the command

/build

/build full

/build degrade-with-note

Type it bare, or paste it with loose context after — Claude figures out the rest.

Solves

A buildable plan sits on disk. Nothing ships until someone writes code and PRs and gates prod.

Payoff

Reads the plan and ships it. Runs the whole cycle so you can watch instead of type.

Takes in

A goal slug pointing to a spec on disk

Returns

One PR per user story
Verify report
Reviewer sign-off
Prod deploy gated on a human

Runs with

—

Needs first

—

Called by

—

Deep dive — 5 sections · ~496 words · original SKILL.mdScroll for tutorial ↓

What it does

Closes the substrate gap between /launch (which produces Construction iteration-goal drafts) and a deployed working app. Tonight: Phase 0-3 LIVE, Phase 4-7 STUB. Live execution ships in follow-up goal AFTER operator-supervised first run.

Read every relevant ADR in architecture/decisions/ before confirming scope. If your scope deviates from any ADR's decision or constraints, surface the deviation as the first agenda item — operator decides amend-ADR vs. revise-scope.

Read the full skill

The complete instructions live at .claude/skills/build/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.

Where in the SDLC

Also relevant in: Test.

Why this phase: Composer that ships a buildable plan — dispatches per-user-story Builder + runs /verify + opens PRs.

Skills catalog — browse all skills grouped by lifecycle phase
Tier system — what each tier gives you

FAQ

Terms from bassclef vocabulary that appear on this page.

luminary: A design or engineering thinker whose discipline bassclef borrows as a review lens — the practitioner in the cameo pattern above. Cooper for personas, Norman for signifiers, Feathers for characterization tests, Beck for TDD rhythm, plus about 90 others. Skills invoke a lens to check work against a specific discipline. `/luminary` browses the catalog. See: /docs/skills/luminary, doi:10.5281/zenodo.22145491
primitive: A building block of bassclef — a skill, a rule, a hook, a luminary, or an agent. Adopters compose primitives into workflows. The lite tier ships one primitive of each kind (except luminaries — lite ships 4, standard adds more, ultra loads the full 96). See: /docs/config/tier-system
load-bearing: A part of the system that other parts depend on — remove it and downstream things break. Bassclef uses the word for artifacts that other artifacts read: a canvas is load-bearing when a spec cites it, a spec is load-bearing when Builder uses it. Plain equivalent: 'actually used' or 'counted on'.
composer: A bassclef skill that runs other skills as a chain. `/launch` composes `/interpret-input` + `/luminary` + `/stage` + `/spec` + `/decompose`. `/build` composes `/verify` + Builder dispatch. You invoke the composer; it invokes its parts. See: /docs/skills/launch, /docs/skills/build
GRASP: Craig Larman's General Responsibility Assignment Software Patterns — 9 principles for assigning responsibility to objects (Information Expert, Creator, Controller, Low Coupling, High Cohesion, Polymorphism, Pure Fabrication, Indirection, Protected Variations). `/decompose` uses GRASP to identify interfaces + responsibilities from a spec.
rule: A markdown file auto-loaded into every session's context. Rules pin discipline the agent applies to every response (plain-English writing, blocked-items protocol, temperance gates). Different from a hook — rules are steering; hooks are enforcement.
skill: A user-invocable command (like `/kiss` or `/temperance`) that runs a specific bassclef workflow. Every skill lives at `.claude/skills/<name>/SKILL.md` with frontmatter + procedure. Adopters type the slash command; Claude Code loads the skill and runs it.
adopter: A repo that has bassclef installed — either via `bassclef init` (lite tier from npm) or via the symlink pattern (standard tier with an Anthropic key). Bassclef's discipline: never break adopters. Every change to a downstream-observable surface ships with a compat shim.
bassclef-upstream: The private repo where bassclef substrate is authored. Ships to a public `bassclef` npm package + a public `bassclef-web` docs site. Adopters read the public tier; the operator maintains upstream.

Shipped by @kingofrock · Read the essays