/use-case
Produce Cockburn-style use cases — main success scenario, numbered extensions, preconditions, postconditions, and stakeholders. Closes the gap between /user-stories and /spec. Distinct from /task-scenarios (UX narrative).
/use-caseType it bare, or paste it with loose context after — Claude figures out the rest.
Requirements go straight to code without a main success scenario. Extension paths get invented per PR.
Cockburn-style use cases with numbered extensions and pre/postcondition contracts.
Takes in
- A feature or persona-scoped scope
Returns
- Fully-dressed use case
- Main success scenario plus extensions
- Pre/postconditions
What it does
Produce goal-level behavior specs in the fully-dressed format per @luminary alistair-cockburn (Writing Effective Use Cases, 2000). Forces systematic extension enumeration (1a, 1b, 2a), surfaces preconditions + postconditions as first-class fields, captures stakeholders + interests so non-actor concerns (compliance, audit, -ilities) reach /decompose.
have produced upstream artifacts
Read the full skill
The complete instructions live at .claude/skills/use-case/SKILL.md in your repo after bassclef-sync. Open with your editor for phases, rules, and worked examples.
Where in the SDLC
Why this phase: Cockburn-style use cases with extensions + pre/postconditions.
Related
- 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
- 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.
- 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.
- 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
/stage
Turn an idea into clickable mock variants on a deployed subdomain. Two sizes: quick (~30 min, 2 variants) and light (~2h, 3 variants plus an Anthropic baseline). Operator picks a direction from phone before committing to build work.
/user-stories
Produce INVEST-shaped user stories that trace back to personas, JTBDs, and value-prop-canvas entries. Backlog-intake artifact for incremental delivery. Distinct from /task-scenarios (UX narrative) and /use-case (system behavior).