What problem does it solve?
Pitch decks are easy to write badly: they overflow visually, lack a coherent narrative, make unsupported market claims, and include traction/team numbers that can’t be defended during diligence.
Core Features & Use Cases
- No-fabrication brief intake (deck-brief): converts founder-provided refs into a structured BRIEF.md so the drafter can’t invent numbers, names, logos, or assets.
- Lifecycle deck production (deck-draft → deck-review → deck-revise): creates Marp slide source plus speaker notes, then scores problem clarity, traction/proof, and team credibility with a critical-flag gate.
- Deck-specific multi-critic review: runs parallel critics for narrative arc, ask specificity, market math/differentiation, and design polish, then aggregates their findings into an advance/block verdict.
- Rendered-artifact validation (deck-figures + deck-design + deck-vision): renders figures and deck.pdf, then checks rendered-only issues like overflow, label cropping, axis legibility, palette adherence, and mathtext artifacts.
Quick Start
Run the full lifecycle for a thread named acme-seed by executing deck-brief acme-seed, then deck-draft acme-seed, then deck-figures acme-seed, then deck-review acme-seed, and finally deck-revise acme-seed until the verdict advances.