From pm-finance
Build the narrative and slide structure for an investor pitch deck. Use when asked to create a pitch deck, investor presentation, fundraising deck, or startup pitch. Produces a slide-by-slide structure with narrative beats, key messages, and what each slide must prove to an investor.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-finance:investor-pitch-deckThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Builds the complete narrative and slide structure for an investor pitch deck — focused on what investors need to see, not what founders want to show.
Builds the complete narrative and slide structure for an investor pitch deck — focused on what investors need to see, not what founders want to show.
For each slide:
Slide 1: Cover — Proves you can say what you do in one sentence. Slide 2: Problem — Proves the problem is real, painful, and large. Lead with the human problem, not market size. Slide 3: Solution — Proves your solution is meaningfully better. Focus on outcome, not features. Slide 4: Product — Proves this is real and works. Show the actual product. Slide 5: Traction — Proves people want this. Show retention and revenue, not signups. Slide 6: Market — Proves the market is large enough. Use bottoms-up TAM where possible. Slide 7: Business Model — Proves you understand unit economics. Include CAC and LTV. Slide 8: Go-To-Market — Proves you can acquire customers efficiently. Focus on what is actually working. Slide 9: Competition — Proves you understand the landscape. Never say "no competitors." Slide 10: Team — Proves this team can execute this opportunity. One sentence per person, specific. Slide 11: Financials — Proves you understand your business. Show assumptions, not just projections. Slide 12: The Ask — Proves you know exactly what you need. Specific use of funds and 18-month milestones.
npx claudepluginhub mileadev/pm-claude-skills --plugin pm-finance2plugins reuse this skill
First indexed Jul 8, 2026
Guides completion of development work by verifying tests, detecting environment, and presenting structured options for merge, PR, or cleanup.
Guides creation and editing of skills using test-driven development with pressure scenarios and subagents to verify agent compliance.
Dispatches multiple subagents concurrently for independent tasks without shared state. Use when facing 2+ unrelated failures or subsystems that can be investigated in parallel.