/sprint

Show what's in flight and what's next. Reads project state, open issues, and the active goal. Proposes the next sprint at thread level, not just the nearest leaf. Run at session start.

Copy the command

/sprint

/sprint default

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

Solves

Session-start orientation takes a full read of git log and whereami and open PRs. Slow.

Payoff

One glance at what's in flight and what's next and what's blocked. Reads project state once.

Takes in

Optional focus flag

Returns

In-flight goals plus PRs
Next-work proposals
Blocked items surfaced

Runs with

/value-prop /kiss /roadmap-reconcile

Needs first

—

Called by

—

Deep dive — 14 sections · ~1,151 words · original SKILL.mdScroll for tutorial ↓

What it does

A quick session-start view of the project. Where you are and what to do next.

/sprint reads the active goal. It walks the parent-goal thread. It checks the parent roadmap. It lists open issues by tier. It proposes 3-4 shapes with trade-offs.

Read the full skill

The complete instructions live at .claude/skills/sprint/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: Concept, Design, Build, Test, Ship, Operate, Adopt.

Why this phase: Session-start orient regardless of active phase — sprint planning composer that crosses the rest of the lifecycle for at least a major portion of it. Home = Planning because that's what the skill produces.

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
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'.
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.
chronicle: A narrative log of what a session shipped — what worked, what did not, what got deferred. Written at session-end. Bassclef's chronicles live under `docs/chronicles/YYYY-MM-DD-slug.md`. Chronicles are how future sessions understand context that the code alone cannot show. See: /docs/skills/session-log
whereami: The authoritative project-state snapshot — current phase, active goals, subsystem status, gate progress, session recap history. Read at session-start; updated at session-end. The one file every new session should read first to know where the project stands. See: /docs/skills/whereami
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.
session log: Same shape as a chronicle — narrative record of what a session shipped. `/session-log` skill drafts it from the session's commits + branch state. Feeds into `/journal` when the operator wants an audience-tuned draft. See: /docs/skills/session-log

Shipped by @kingofrock · Read the essays