/requirement
Produce Cockburn use cases plus INVEST user stories for a feature in one pass. The writer produces formal use cases for a spec. The picker produces INVEST stories for a backlog. You get both from one operator input. Combines /use-case + /user-stories.
/requirement/requirement both/requirement use-case-only/requirement story-onlyType it bare, or paste it with loose context after — Claude figures out the rest.
Features get built from a one-line ticket. Corners get cut. Acceptance drifts from what the persona needs.
Cockburn use cases plus INVEST user stories in one pass. Written for a writer-style adopter.
Takes in
- A feature name or ticket ref
Returns
- Fully-dressed use cases
- INVEST user stories with acceptance criteria
What it does
You describe a feature in a paragraph. /requirement returns two artifacts.
{/* FKGL-EXEMPT: structured shape enumeration; the parentheticals name the artifact fields */}
Read the full skill
The complete instructions live at .claude/skills/requirement/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 use cases + INVEST user stories in one pass.
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.
- 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
/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.
/riff
Produce 2 or 3 clickable mock variants. Each pins a luminary lens. Three modes — full, local, scratch. Full uses git, gh, and screenshots. Local writes to disk only. Scratch uses a tmp dir with no git.