@thebassclef/lite 1.0.4 → 1.1.1

package/dist/lite/.claude/skills/lean-canvas/SKILL.md

@@ -0,0 +1,332 @@
+---
+tier: lite
+name: lean-canvas
+description: "Produce a Lean Canvas \u2014 Ash Maurya's 9-box template \u2014 filled through persona lenses. Two modes: commercial (revenue in dollars) and growth-loop (audience plus credibility). Outputs the riskiest assumption to validate next."
+problem: "New products get built without naming the customer or the problem or the unfair advantage."
+value: "Ash Maurya's 9-box canvas filled through persona work. One page names the business."
+inputs: [Personas file, Value proposition data, A rough product idea]
+outputs: [Lean Canvas 9-box filled, Problem and solution named per persona]
+user_invocable: true
+disable_model_invocation: false
+modes: [commercial, growth-loop]
+---
+
+# /lean-canvas — Ash Maurya's 9-box business model template
+
+Use this skill when an idea is early enough that the business model isn't proven yet. Lean Canvas asks "does this hold together at all" before product work asks "what should we build."
+
+Distinct from `/canvas` (Roman Pichler — product vision and feature shape) and `/value-prop` (April Dunford — message positioning). All three compose. Lean Canvas comes first when business model fit is uncertain.
+
+## When to use
+
+- A new initiative or product where revenue + customer + channel assumptions aren't yet validated
+- A strategic move (open-source launch, audience play, growth loop) where "does this hold together" is the load-bearing question
+- Pre-Phase-XI scope work where Solution-first thinking risks Innovator's Bias
+- An existing goal that needs the riskiest assumption named explicitly before more building
+
+## When NOT to use
+
+- Product-detail work where business model is already validated → use `/canvas` (Pichler)
+- Sharpening the message for a validated value prop → use `/value-prop` (Dunford)
+- Customer-discovery research at the task-level → use `/jtbd-tasks` or `/task-scenarios`
+- An incremental feature inside an existing product line → too small for Lean Canvas; `/spec` is enough
+
+## Usage
+
+```
+/lean-canvas <slug> [--start-with <box>] [--personas <list>] [--commercial | --growth-loop]
+```
+
+| Arg | Required | Default |
+|---|---|---|
+| `<slug>` | yes | — |
+| `--start-with` | no | prompts operator |
+| `--personas` | no | sam, jamie, morgan |
+| `--commercial` or `--growth-loop` | no | prompts operator |
+
+Examples:
+
+```
+/lean-canvas bassclef-public-launch --start-with problem --personas sam,jamie,morgan --growth-loop
+/lean-canvas openclaw-titans-memory --start-with solution --personas sam,morgan
+/lean-canvas your-product --start-with customer-segments --personas operator,boss --commercial
+```
+
+## The 9 boxes
+
+Ash Maurya's adaptation of Osterwalder's Business Model Canvas.
+
+| # | Box | Question it answers |
+|---|---|---|
+| 1 | Problem | Top 1-3 problems the customer segment faces |
+| 2 | Customer Segments | Who has the problem; early adopters specifically |
+| 3 | Unique Value Proposition | Single clear message — why this is different and worth attention |
+| 4 | Solution | Top 3 features that address the top 3 problems |
+| 5 | Channels | Path to customer segment |
+| 6 | Revenue Streams | How value gets captured (extended in growth-loop mode) |
+| 7 | Cost Structure | What it costs to maintain and grow |
+| 8 | Key Metrics | Measurable signals the business is working |
+| 9 | Unfair Advantage | What cannot be easily copied or bought |
+
+## Procedure
+
+### Step 1 — Confirm scope
+
+Ask: what are we canvasing? A new product? A strategic move? A pivot? Capture the operator's one-sentence framing.
+
+### Step 2 — Confirm personas
+
+Default: Sam (mid-engineer), Jamie (tech PM), Morgan (senior staff engineer) from `strategy/personas/`. Operator can override with their own personas. The discipline (multi-persona reads on key boxes) stays.
+
+### Step 3 — Confirm framing: commercial or growth-loop
+
+Ask: "Is this a commercial product (revenue = dollars) or a growth-loop / credibility / community venture (revenue = audience + credibility + optionality)?"
+
+In growth-loop mode, Revenue Streams accepts:
+
+- Audience accumulated
+- Credibility surfaces created
+- Optionality unlocked (PE, executive role, board seat, advisory)
+- Citations, conference invites, inbound DMs from target audience
+
+Key Metrics in growth-loop mode accepts:
+
+- Subscriber growth
+- GitHub stars / PR-author diversity
+- Citation counts
+- Inbound DMs from target audience
+
+### Step 4 — Idea backstory
+
+Operator describes the idea's origin in 2-3 sentences. Capture verbatim in the chain-of-beliefs file (this becomes the historical anchor when the canvas evolves).
+
+### Step 5 — Starting box
+
+Operator picks. Skill notes the implicit risk priority:
+
+- **Start with Problem** → testing desirability first. Maurya's recommended fill order for validating an idea.
+- **Start with Customer Segments** → testing audience fit first. Common for growth-loop bets.
+- **Start with Solution** → **flag Innovator's Bias risk.** Tell the operator: "You're starting with Solution. This is common but creates a real risk — you may write Problem statements that justify the Solution you already want. Continue, but revisit Problem and Customer Segments critically after the first pass."
+- **Other boxes** → operator's call; skill notes the assumption being tested first.
+
+### Step 6 — 20-minute fill
+
+Walk box-by-box in operator's chosen order. For each box where multi-persona reads matter (Problem, UVP, Channels, Unfair Advantage — see PERSONA-REQUIRED below), ask each persona's read separately. Don't synthesize a single answer; surface where personas converge and where they diverge.
+
+20-minute target for first pass. Boxes can be blank. Iterate after operator reflection.
+
+### Step 7 — Persona-convergence check
+
+Highlight boxes where personas diverged. Ask the operator: is the divergence reflecting a real customer segment split, or is the box's framing unclear?
+
+Convergence is a strong signal. Divergence is a finding to capture, not a flaw to smooth over.
+
+### Step 8 — Chain-of-beliefs classification
+
+Walk each belief in the canvas. Ask operator to classify:
+
+- **Leap-of-faith** — a strong assumption with no evidence yet
+- **Anecdotal observation** — based on one or two real customer signals, not yet systematic
+- **Fact-with-evidence** — measured, repeatable, defensible
+
+### Step 9 — Riskiest assumption
+
+Skill proposes the riskiest leap-of-faith. Operator confirms or overrides. The riskiest assumption is the next thing to validate — not the next thing to build.
+
+### Step 10 — Next validation move
+
+Skill suggests an experiment shape matched to the riskiest-assumption type:
+
+- Problem belief → customer interviews (5-10, scripted)
+- Customer segment belief → audience-targeting test (ad spend, channel pilot)
+- UVP belief → smoke test landing page + signup conversion
+- Solution belief → smallest functional prototype + observe use
+- Channel belief → single-channel pilot before scaling
+- Revenue belief → pricing-page test or pre-order page
+- Cost belief → bottoms-up estimate vs spike-test build
+- Metric belief → instrument and observe baseline before optimizing
+- Unfair advantage belief → competitive teardown or "how hard would it be to copy" red-team
+
+### Step 11 — Write outputs
+
+Two files:
+
+1. `docs/operator-private/canvases/<slug>-lean-canvas.md` — the canvas itself
+2. `docs/operator-private/canvases/<slug>-chain-of-beliefs.md` — fill order + classification + riskiest assumption + next move
+
+If the operator requests a non-default path, honor it. Apply /kiss discipline throughout — grade-10 English, plain words, reserved concept names from the four-name system (substrate, bassclef, cameo, Studio, Band, bandleader) excepted per bassclef#763.
+
+## PERSONA-REQUIRED boxes
+
+These four boxes get multi-persona reads (not a single synthesized answer):
+
+- **Problem** — what does each persona see as the problem?
+- **Unique Value Proposition** — what message lands for each persona?
+- **Channels** — how does each persona find products like this?
+- **Unfair Advantage** — what does each persona think can't easily be copied?
+
+Other boxes can use single-perspective reads unless operator opts in to multi-persona.
+
+## Output shape
+
+### File 1: `docs/operator-private/canvases/<slug>-lean-canvas.md`
+
+```markdown
+---
+title: <human-readable title>
+slug: <slug>
+date: 2026-MM-DD
+framing: commercial | growth-loop
+personas: [list]
+starting_box: <box name>
+status: draft | refined | validated
+references:
+  - {type: file, id: docs/operator-private/canvases/<slug>-chain-of-beliefs.md, anchor: belief classification + next validation}
+---
+
+# <Title> — Lean Canvas
+
+## 1. Problem
+
+(persona reads if PERSONA-REQUIRED)
+
+## 2. Customer Segments
+
+## 3. Unique Value Proposition
+
+(persona reads if PERSONA-REQUIRED)
+
+...
+
+## Convergence and divergence
+
+Where personas agreed:
+
+Where personas diverged:
+```
+
+### File 2: `docs/operator-private/canvases/<slug>-chain-of-beliefs.md`
+
+```markdown
+---
+title: <Title> — chain of beliefs
+slug: <slug>-chain-of-beliefs
+date: 2026-MM-DD
+canvas: docs/operator-private/canvases/<slug>-lean-canvas.md
+status: draft | refined | validated
+---
+
+# <Title> — chain of beliefs
+
+## Idea backstory
+
+(operator's 2-3 sentence origin verbatim)
+
+## Fill order
+
+1. <box>
+2. <box>
+3. ...
+
+## Beliefs classified
+
+| Box | Belief | Classification |
+|---|---|---|
+| Problem | ... | leap-of-faith / anecdotal / fact-with-evidence |
+| ... |
+
+## Riskiest assumption
+
+<one paragraph>
+
+## Suggested next validation move
+
+<one paragraph naming the experiment shape>
+```
+
+## Composes with
+
+- `/personas` — pulls persona files from `strategy/personas/` as default customer-segment lenses
+- `/value-prop` — UVP box ingests `/value-prop` output. When `/value-prop` has not yet run for this canvas, UVP box stays empty and the canvas closeout step BLOCKs until UVP is set; the skill points at `/value-prop` for deeper UVP development.
+- `/canvas` — Pichler's product canvas; `/lean-canvas` output feeds product-detail work downstream once business model is validated
+- `/kiss` — applied throughout for plain-language discipline on canvas outputs
+- `/value-prop-canvas` — Strategyzer's Value Proposition Canvas is the Problem + UVP + Customer Segments boxes expanded; compose `/lean-canvas` first for business model fit, VPC second for product-market fit
+
+## Distinct from
+
+- `/canvas` — Pichler's product canvas (Vision → Target → Stand-Out → Big Picture → Critical Questions). Product-detail level; assumes the business model holds. `/lean-canvas` is upstream.
+- `/value-prop` — Dunford's positioning framework. Sharpens the UVP into a market-ready message. `/lean-canvas` produces the UVP raw; `/value-prop` polishes it.
+- `/value-prop-canvas` — Strategyzer's VPC. Zooms into Problem + UVP + Customer Segments with Jobs/Pains/Gains and Products/Pain-relievers/Gain-creators. Use after `/lean-canvas` when product-market fit is the question.
+- `/personas` — produces persona files. `/lean-canvas` consumes them as customer-segment lenses; doesn't create personas.
+
+## Rules
+
+- Skill ALWAYS produces two files (canvas + chain-of-beliefs); never just one.
+- Skill ALWAYS surfaces the operator's idea backstory verbatim in the chain-of-beliefs file.
+- Skill ALWAYS flags Innovator's Bias risk when operator starts with Solution.
+- Skill ALWAYS asks for each persona's read on PERSONA-REQUIRED boxes; never synthesizes a single answer.
+- Skill ALWAYS proposes the riskiest assumption; operator confirms or overrides — silence is not confirmation.
+- Skill ALWAYS suggests a validation experiment matched to the riskiest-assumption type.
+- Skill NEVER auto-commits the output files. Operator reviews and commits.
+- Skill NEVER fills boxes from training priors. If the operator's input is thin for a box, ask; don't infer.
+- Skill RESPECTS operator-private content. Default output path `docs/operator-private/canvases/` is gitignored — content stays local. If the operator wants a canvas in the public tree, they request `strategy/canvases/` explicitly. The skill surfaces this choice when content looks operator-private (Fortune 50 employer references, specific personal optionality moves, day-job-adjacent context).
+- Skill APPLIES /kiss discipline throughout — grade-10 English, plain words, reserved concept names from the four-name system excepted per bassclef#763.
+
+## Examples
+
+### Example 1 — Commercial product, Problem-first
+
+```
+/lean-canvas your-product --start-with problem --personas operator,boss --commercial
+```
+
+Walks the 9 boxes starting with Problem. Personas: operator + boss (custom for a two-sided market). Revenue Streams in dollars. Output: `docs/operator-private/canvases/your-product-lean-canvas.md` + `your-product-chain-of-beliefs.md`. Likely riskiest assumption: whether bosses will pay for what operators want.
+
+### Example 2 — Growth-loop venture, Problem-first
+
+```
+/lean-canvas bassclef-public-launch --start-with problem --personas sam,jamie,morgan --growth-loop
+```
+
+Walks the 9 boxes starting with Problem. Personas: the three default bassclef personas. Revenue Streams in audience + credibility + optionality. Key Metrics in subscriber growth + GitHub stars + citations. Output: the strategy doc that informs Phase XVI Tier 0 pitch text + README rewrite + methodology paper shape.
+
+### Example 3 — Solution-first with Innovator's Bias flag
+
+```
+/lean-canvas openclaw-titans-memory --start-with solution --personas sam,morgan
+```
+
+Operator starts with Solution (the most common starting point per Maurya). Skill flags: "Starting with Solution creates Innovator's Bias risk. After first-pass fill, revisit Problem and Customer Segments critically — you may have written Problem statements that justify the Solution you already wanted." Operator continues; second pass refines.
+
+## Sources read
+
+- `.claude/luminaries/ash-maurya.md` — the backing luminary; Running Lean methodology + Lean Canvas 9-box structure
+- Ash Maurya, "What is the Right Fill Order for the Lean Canvas?" — desirability → viability → feasibility for validation; "no right fill order" for ideation
+- Ash Maurya, *Running Lean* (2010, 2nd ed 2012, 3rd ed 2022) — SENTINEL_the_bassclef_reference
+- Ash Maurya, *Scaling Lean* (2016) — Customer Factory model + AARRR Key Metrics
+- `strategy/personas/sam-mid-engineer.md`, `jamie-tech-pm.md`, `morgan-senior-staff-engineer.md` — default persona lenses
+- `strategy/audience-commitment.md` — portfolio-operator audience commitment (informs growth-loop framing)
+- `.claude/skills/canvas/SKILL.md` — Pichler's product canvas (downstream composition target)
+- `.claude/skills/value-prop/SKILL.md` — Dunford's positioning (UVP polish target)
+- `.claude/skills/value-prop-canvas/SKILL.md` — Strategyzer VPC (product-market-fit composition target)
+- bassclef#763 — /kiss hook allowlist for reserved concept names
+
+## Why this skill exists
+
+Bassclef's substrate had three product-strategy skills before this one:
+
+- `/canvas` — Pichler's product canvas (product vision and shape)
+- `/value-prop` — Dunford's positioning (the message)
+- `/value-prop-canvas` — Strategyzer's VPC (product-market fit detail)
+
+None of them asks the upstream question: **does the business model hold together at all?** Without that question answered, product work proceeds on unvalidated assumptions — Solution before Problem, features before customer segments, channels before audience fit.
+
+Maurya's Lean Canvas closes the gap. The 9-box template forces explicit business-model articulation in 20 minutes; the chain-of-beliefs classification names the riskiest assumption that needs testing before more building.
+
+For bassclef's growth-loop strategy specifically (per locked-decisions.md and the 2026-05-25 operator pivot), the Lean Canvas's Revenue Streams + Key Metrics boxes need reframing — audience accumulated, credibility surfaces created, optionality unlocked instead of dollar revenue. Maurya's framework accepts this reframing because the underlying question (which assumptions are riskiest) is general.
+
+INSTEAD of "build the product, hope the business model emerges," dispatch `/lean-canvas` first. Validate the model holds together. Identify the riskiest assumption. Validate it before building.
+
+## Output discipline
+
+Dispatch `/kiss words --rewrite` on your skill output before you return it. See `standards/skill-output-discipline.md` for the contract.