/launch

Compare variants of an idea. Get a mock gallery. Pick a direction. Get a spec, user stories, and a plan to build. Two sizes — medium and full. Three modes — full, local, scratch.

Copy the command

/launch

/launch full

/launch local

/launch scratch

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

Solves

An idea is a doc. A working feature is code. The gap in between is where projects stall.

Payoff

Turns an idea into a buildable plan — mock gallery and spec and INVEST stories. Ready for /build.

Takes in

A rough idea or ticket or canvas

Returns

Clickable mock gallery
Buildable spec
INVEST user stories
GRASP responsibility matrix

Runs with

—

Needs first

—

Called by

—

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

What it does

End-to-end workflow for build tiers (medium + full). Takes operator input (paragraph OR a chosen variant from /stage's output via base=<slug>) and produces a PR containing:

Anthropic baseline), each variant page with back-nav to master gallery — same UX continuity as /stage

Read the full skill

The complete instructions live at .claude/skills/launch/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: Build.

Why this phase: Buildable-plan composer — spec + decomposition + prototype gallery.

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.

cameo: A pattern for routing a specific practitioner's documented judgment into a specific software development task. Bassclef implements it as three parts — a curated catalog of practitioners, a matcher that connects problems to relevant experts, and invokable skills that channel the pick. You see 'Cooper says X' or 'Norman flags Y' inline rather than the skill running a full consult. Trades depth for speed on lower-stakes surfaces. See: /docs/skills/luminary, doi:10.5281/zenodo.22145491
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
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
INVEST: Bill Wake's checklist for well-formed user stories — Independent, Negotiable, Valuable, Estimable, Small, Testable. `/ticket` enforces all six for stories. Epics only need V (Valuable) + N (Negotiable) since they break I/E/S/T by definition.
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.
hook: A shell script bassclef wires into Claude Code's tool-invocation lifecycle. Hooks fire at events like PreToolUse (before an Edit lands) or SessionStart (when a session opens). Hooks enforce rules mechanically — a rule says 'don't do X'; a hook fires and BLOCKs if X happens.
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