Skip to content

heyparsadev/claude-venture-plugin / venture/skills/model

This skill should be used when the user asks about business models, unit economics, lean canvas, pricing math, CAC/LTV, break-even, or financial projections — e.g. "build a lean canvas", "calculate unit economics", "does the math work", "CAC LTV payback", "revenue projection", "مدل کسب‌وکار", "اقتصاد واحد", "بیزینس مدل", "حساب کن این بیزینس می‌صرفه یا نه", "پیش‌بینی درآمد". Produces a lean canvas, unit economics workbook, and scenario projections in the venture workspace.

FileKindSize
SKILL.mdskill md5.1 KB
references/lean-canvas.mdmarkdown1.6 KB
references/unit-economics-guide.mdmarkdown2.9 KB

references/lean-canvas.md

View on GitHub
# Lean Canvas Template (Ash Maurya)

One page, nine boxes. Each cell cites where it came from (`[discovery]`, `[market]`, `[competitors]`, `[gtm]`, `[assumption]`). TBD beats fabrication.

```markdown
# Lean Canvas — <Venture>
<date> · iteration <N>

## 1. Problem (top 3)
<from discovery synthesis pains table — with frequency×severity rank>
Existing alternatives: <what they use today — from discovery/competitors>

## 2. Customer segments
<target + early adopters specifically: who buys FIRST [discovery]>

## 3. Unique value proposition
<single clear message — reuse positioning statement if GTM ran [gtm]>
High-level concept: <"X for Y" if helpful>

## 4. Solution (top 3 features only)
<mapped 1:1 to the problems above — nothing else belongs here>

## 5. Channels
<from GTM channel selection; else hypothesis [assumption]>

## 6. Revenue streams
<pricing model + price point + rationale [gtm/competitors]>

## 7. Cost structure
<fixed (team, infra, rent) + variable per customer (COGS, support, payment fees)>

## 8. Key metrics
<the 3–5 numbers that show the engine works — match the business type
(e.g. SaaS: signups→activated→retained→paying; marketplace: liquidity, repeat rate)>

## 9. Unfair advantage
<what can't be easily copied or bought: distribution lock-in, proprietary data, community,
regulatory license, founder insight. "None yet" is an honest and common answer — write it
and note the plan to build one.>

---
**Riskiest cell right now:** <which box, why, and the cheapest test for it>
```

Order of filling (matters): 1 → 2 → 3 → 9 → 4 → 5 → 6 → 7 → 8. Problem before solution, always.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall