pitch-deck

Create a pitch deck with structured process, quality checks, and system integration

SKILL.md

GitHub

Pitch Deck

Purpose

Create a comprehensive pitch deck that delivers actionable, measurable results. This skill provides a structured process with quality validation, ensuring professional-grade output every time.

Category: Startup & Entrepreneurship

Inputs

Required

  • Objective: What you want to achieve with this deliverable
  • Context: Relevant background information

Optional

  • Constraints: Any limitations or requirements to consider
  • Existing Work: Previous documents or data to build on

System Context

Before starting:

  • Read memory.md for current project context and priorities
  • Check knowledge-base.md for relevant learned rules or constraints
  • Review any existing related documents in the project
  • Note any active tasks in Task Board.md that relate to this deliverable

Process

Step 1: Context & Research

  • Review any existing pitch deck documents in the project
  • Check knowledge-base.md for relevant learned rules or constraints
  • Check memory.md for current project context and priorities
  • Identify key stakeholders and their requirements
  • Select the most appropriate framework: Lean Startup, Business Model Canvas, Lean Canvas

Step 2: Analysis & Framework Application

  • Apply the selected framework to structure the pitch deck
  • Identify gaps, opportunities, and risks
  • Define success metrics: Monthly Burn Rate, Runway (months), MoM Growth Rate, CAC/LTV Ratio (target: 1:3+)
  • Document assumptions and dependencies
  • Validate approach against industry best practices

Step 3: Build the Deliverable

  • Structure the pitch deck using the output format below
  • Include specific, actionable recommendations — not generic advice
  • Add concrete numbers, timelines, and benchmarks where applicable
  • Cross-reference with existing project documents for consistency
  • Ensure every section adds value — remove filler

Step 4: Quality Validation

  • All required inputs have been addressed
  • Recommendations are specific and actionable (not vague)
  • Numbers and benchmarks are realistic and sourced
  • Output format matches the specification below
  • No contradictions with knowledge-base rules
  • Follows best practice: Talk to 100 potential customers before building

Output Format

# Pitch Deck

## Executive Summary
[2-3 sentence overview of the deliverable and key recommendations]

## Context & Objectives
- **Objective**: [What this achieves]
- **Audience**: [Who this is for]
- **Timeline**: [When this applies]

## Analysis
[Structured analysis using the selected framework]

## Recommendations
1. [Specific, actionable recommendation with expected impact]
2. [Specific, actionable recommendation with expected impact]
3. [Specific, actionable recommendation with expected impact]

## Implementation
| Action | Owner | Timeline | Priority |
|--------|-------|----------|----------|
| [Action item] | [Who] | [When] | [High/Medium/Low] |

## Success Metrics
| Metric | Current | Target | Measurement Method |
|--------|---------|--------|-------------------|
| [KPI] | [Baseline] | [Goal] | [How to measure] |

## Risks & Mitigations
| Risk | Likelihood | Impact | Mitigation |
|------|-----------|--------|------------|
| [Risk] | [H/M/L] | [H/M/L] | [Action] |

## Next Steps
- [ ] [Immediate next action]
- [ ] [Follow-up action]
- [ ] [Review date]

Applicable Frameworks

  • Lean Startup
  • Business Model Canvas
  • Lean Canvas
  • Product-Market Fit Engine
  • Venture Capital Method
  • TAM/SAM/SOM

Key Metrics

  • Monthly Burn Rate
  • Runway (months)
  • MoM Growth Rate
  • CAC/LTV Ratio (target: 1:3+)
  • Activation Rate
  • Sean Ellis Test (40%+ very disappointed)

Best Practices

  • Talk to 100 potential customers before building
  • Default alive vs default dead — know your status
  • Focus on one metric per stage
  • 18 months runway minimum after raising
  • Weekly team updates, monthly investor updates

After Completion

  • Update memory.md if this deliverable changes project context or priorities
  • Add any reusable learnings to knowledge-nominations.md
  • If follow-up actions were identified, add them to Task Board.md
  • Recommend related skills if additional work is needed