/value-prop
Draft a value prop for a ticket, goal, or feature. Three sizes: tweet (≤280 chars claim + sharpener), brief (claim + 3 reasons), verbose (full Dunford / Moore positioning). Pick the size that matches your audience attention.
/value-prop/value-prop flash/value-prop tweet/value-prop brief/value-prop verboseType it bare, or paste it with loose context after — Claude figures out the rest.
PR bodies and ticket bodies open with solution-framing. The reader has no reason to care.
One line that names claim plus sharpener. Three sizes — tweet and brief and verbose.
Takes in
- A ticket ref or doc path or scope description
- Optional size — tweet or brief or verbose
Returns
- Claim plus sharpener at chosen size
- Ready to paste as opener
What it does
A value proposition for a ticket, iteration goal, feature, or product concept. Three sizes along a single axis — how much scaffolding around the claim? tweet gives you a claim plus one sharpener in ≤280 chars for status updates and Slack. brief (default) gives you a ≤180-char claim plus 3 evidence-backed Reasons to Believe plus sources — deck-ready. verbose gives you the full Dunford 5-part sales pitch plus Moore positioning — long-form material for landing pages and pitches.
Any time you need to state the value of a ticket or feature at a specific size. Pick the size by audience attention:
Read the full skill
The complete instructions live at .claude/skills/value-prop/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: Design, Ship.
Why this phase: Value-prop drafting. Concept-time framing; composes into pitches + PR bodies.
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
- 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.
Shipped by @kingofrock · Read the essays
/temperance
Pause and think before you code. Asks — am I building the right thing AND building it the right way? Fires before every non-trivial action.
/lean-canvas
Produce a Lean Canvas — Ash Maurya's 9-box template — filled through persona lenses. Two modes: commercial (revenue in dollars) and growth-loop (audience plus credibility). Outputs the riskiest assumption to validate next.