Pitch Deck
Create a structured pitch deck outline for investors, stakeholders, or partners. Covers problem, solution, market, traction, team, and ask. Natural output after PRD + Problem Stress Test validation.
Best use case
Pitch Deck is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a structured pitch deck outline for investors, stakeholders, or partners. Covers problem, solution, market, traction, team, and ask. Natural output after PRD + Problem Stress Test validation.
Teams using Pitch Deck should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/pitch-deck/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How Pitch Deck Compares
| Feature / Agent | Pitch Deck | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create a structured pitch deck outline for investors, stakeholders, or partners. Covers problem, solution, market, traction, team, and ask. Natural output after PRD + Problem Stress Test validation.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Skill: Pitch Deck ## Metadata | Field | Value | |-------|-------| | **Skill ID** | SKL-0036 | | **Version** | 1.0 | | **Owner** | product-manager | | **Inputs** | PRD/GDD, stress test, competitor analysis, DECISIONS.md | | **Outputs** | `docs/PITCH_DECK.md`, STATE.md updated | | **Triggers** | `PITCH_DECK_REQUESTED` | --- ## Purpose After the idea has been validated (Problem Stress Test) and designed (PRD/GDD), the user may need to pitch it — to investors, stakeholders, co-founders, or potential users. This skill produces a structured pitch deck outline following the format VCs and angel investors expect to see. --- ## Procedure ### Step 1 — Gather Context Read available documents: 1. `docs/PRD.md` or `docs/GDD.md` — problem, solution, users, scope 2. `docs/PROBLEM_STRESS_TEST.md` — validation verdict and strengths 3. `docs/COMPETITOR_ANALYSIS.md` — market landscape and differentiation 4. `DECISIONS.md` — key product decisions If minimal context exists, interview the user for missing pieces. ### Step 2 — Build the Deck (12-Slide Structure) Write each slide as a section in `docs/PITCH_DECK.md`: **Slide 1: Title** - Company/product name - One-line tagline (from PRD elevator pitch or GDD core fantasy) - Your name and role **Slide 2: Problem** - The problem in the user's language (not technical jargon) - How many people have this problem (scale) - How they're solving it today (painful workarounds) - Source: PRD Problem Statement or Problem Stress Test Lens 3 **Slide 3: Solution** - Your solution in one sentence - 3 key features that address the problem - Demo screenshot or mockup description (placeholder) - Source: PRD MVP Scope or GDD Core Mechanics **Slide 4: Market Size** - TAM (Total Addressable Market) - SAM (Serviceable Addressable Market) - SOM (Serviceable Obtainable Market) - Source: web research + PRD target users **Slide 5: Business Model** - How you make money - Pricing model - Unit economics (if known): LTV, CAC, margins - Source: PRD or user interview **Slide 6: Traction** - What you've built or shipped so far - Users, revenue, or engagement metrics (if any) - Key milestones achieved - If pre-launch: validation signals (conversations, waitlist, LOIs) **Slide 7: Competition** - Competitive landscape (2x2 matrix or comparison table) - Your differentiation (primary differentiator) - Source: COMPETITOR_ANALYSIS.md **Slide 8: Go-to-Market** - How you'll acquire your first 100 users - Growth strategy (organic, paid, partnerships, community) - Distribution advantage (if any) **Slide 9: Team** - Founder(s) background — why are you the right people? - Key hires needed - Advisors (if any) **Slide 10: Financials** - Revenue projections (if applicable) - Key assumptions - Burn rate and runway (if applicable) **Slide 11: The Ask** - How much are you raising? - What will the money be used for? (hire, build, market) - What milestones will it fund? **Slide 12: Closing** - Contact information - One powerful closing statement (not "thank you" — use Uri Levine's advice: put your strongest argument on the last slide) ### Step 3 — Apply Uri Levine's Pitch Principles Review the deck against these rules: - **First and last slides get the most screen time** — make them count - **Lead with the problem narrative** — the problem story is more compelling than the solution description - **Emotional engagement** — investors should envision using the product themselves - **Expect 100 rejections** — the deck should be tight enough to survive brutal Q&A ### Step 4 — Write to docs/PITCH_DECK.md Include a note at the top: ```markdown > This is a pitch deck **outline**, not a slide file. Use it as the content > source for your actual presentation tool (Google Slides, Keynote, Figma, etc.). > Each section = one slide. ``` ### Step 5 — Update STATE.md --- ## Constraints - Produces an outline document, not actual slides (no PowerPoint/Keynote generation) - Financial projections are frameworks, not predictions — clearly label assumptions - Market size estimates use available data — flag if numbers are rough - Does not fabricate traction or metrics — if pre-launch, say so honestly - Never makes promises the product can't keep --- ## Primary Agent product-manager --- ## Definition of Done - [ ] All 12 slides have content - [ ] Problem slide uses user language, not jargon - [ ] Solution slide is one sentence + 3 features - [ ] Market size includes TAM/SAM/SOM - [ ] Competition slide has comparison (matrix or table) - [ ] Ask slide is specific (amount + use of funds) - [ ] Closing slide has a strong statement (not "thank you") - [ ] Uri Levine pitch principles applied - [ ] Written to docs/PITCH_DECK.md - [ ] STATE.md updated ## Output Contract | Field | Value | |-------|-------| | **Artifacts** | `docs/PITCH_DECK.md` (12-slide outline) | | **State Update** | `.claude/project/STATE.md` — mark task complete, log files modified | | **Handoff Event** | `TASK_COMPLETED` (pitch deck outline complete) |
Related Skills
Supply Chain Audit
Audit the dependency supply chain for security risks beyond what `npm audit` or `pip audit` catches. Analyzes dependency health, maintainer trust signals, typosquatting risk, and transitive dependency exposure.
SEO Audit
Audit web pages for search engine optimization: meta tags, heading hierarchy, structured data, image optimization, mobile-friendliness, and content quality. Complements SKL-0013 (Growth & Distribution) by validating what was built.
Launch Checklist
Pre-launch validation covering everything deployment (SKL-0021) doesn't: analytics, error tracking, social meta, legal pages, email setup, DNS, SSL, and go-live readiness. Produces a launch readiness report with pass/fail checklist. Use this skill before going live on any project.
Insecure Defaults Detection
Detect insecure default configurations, hardcoded credentials, fail-open security patterns, and dangerous default values in application code and configuration files. Complements SKL-0015 (Security Audit) by focusing on configuration-level vulnerabilities that dependency scanners miss.
Differential Security Review
Security-focused review of code changes using git diff analysis. Identifies security implications of recent modifications — new attack surfaces, removed protections, changed auth logic, and risky refactors. Complements SKL-0016 (Code Review) with a security lens on diffs.
Copywriting
Write conversion-focused copy using proven frameworks (AIDA, PAS, BAB). Produces headlines, CTAs, landing page copy, email sequences, and micro-copy. Ensures copy matches brand voice and target audience.
Competitor Analysis
Structured competitor research: features, pricing, positioning, gaps, and differentiation strategy. Feeds into PRD Writing (SKL-0004) and Problem Stress Test (SKL-0027) with better market context.
UX Design
Design user experiences including wireframes, flows, and interaction patterns. Use this skill when UX design work is requested, including onboarding flows and interface layouts.
User Acceptance Testing
Structured QA testing with four modes: diff-aware (auto-scoped to branch changes), full (systematic exploration), quick (30-second smoke test), and regression (compare against baseline). Produces health score, structured reports, and actionable bug lists. Use this skill when UAT is requested or a feature is ready for acceptance testing.
Token Audit
Audit the current project for token waste patterns. Produces a Token Health Report with scored findings and actionable fixes. Use this skill when token usage feels high, sessions are hitting limits, or before optimizing costs.
Test Writing
Write automated tests for existing or new functionality. Use this skill when tests are requested, including unit tests, integration tests, and end-to-end tests.
Skill Creator
Turn a repetitive workflow into a reusable custom skill. Interviews the user, then produces a complete SKILL.md with frontmatter, procedure, constraints, definition of done, and output contract in custom-skills/. Use this skill when you find yourself repeating the same process and want to automate it.