@openpresentation/opf 0.18.3 → 0.19.0

package/dist/spec/catalogs/narratives/persuasive-sales.json

@@ -1,87 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "persuasive-sales",
-  "name": "Persuasive Sales",
-  "summary": "Top-of-funnel sales arc that creates awareness and alignment with a prospective customer. Anchored in a market change, leading to your unique capabilities, supported by proof, ending with a clear call to action.",
-  "audienceFit": [
-    "prospects",
-    "customers",
-    "buyers"
-  ],
-  "duration": {
-    "min": 15,
-    "max": 45
-  },
-  "tags": [
-    "sales",
-    "go-to-market",
-    "outbound",
-    "discovery"
-  ],
-  "beats": [
-    {
-      "id": "intro",
-      "name": "Introduction",
-      "description": "Open with a brief framing of who you are and why this conversation is worth the prospect's next thirty minutes. Keep credentials short; the audience cares about their problem, not your résumé.",
-      "instructions": "Name & logo",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "big-change",
-      "name": "Big Change",
-      "description": "Name the market shift the prospect's industry is living through. Make it concrete, recent, and undeniable. The change — not the product — is the reason they should care.",
-      "instructions": "Highlight market shift",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "response-to-change",
-      "name": "Winners and Losers",
-      "description": "Show how the change is creating winners and losers in the prospect's space. Use named examples where you can. The goal is for the prospect to wonder which side they'll end up on.",
-      "instructions": "Show winners & losers",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "benefits",
-      "name": "Benefits",
-      "description": "Paint the outcome a winner experiences: a vivid picture of the prospect's life on the other side of the change. Lead with what changes for them, not with what your product does.",
-      "instructions": "Describe benefits, paint a vivid picture",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "capabilities",
-      "name": "Capabilities",
-      "description": "Reveal the unique capabilities that make those outcomes possible. Frame them as the 'magic gifts' the prospect needs to win the new game. Highlight what's structurally different from the alternatives.",
-      "instructions": "Present unique features as 'magic gifts' to the customer",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "evidence",
-      "name": "Evidence",
-      "description": "Share customer testimonials, case studies, and measurable outcomes from organizations like the prospect's. Pick evidence that maps to the benefits you promised, not generic logos.",
-      "instructions": "Share testimonials",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "call-to-action",
-      "name": "Call to Action",
-      "description": "Ask for the next step in the sales process. Be specific: a pilot, a workshop, a follow-on conversation with a named stakeholder. Make the smallest credible commitment that keeps momentum.",
-      "layout": "title",
-      "instructions": "Encourage decision-making",
-      "type": "text"
-    },
-    {
-      "id": "close",
-      "name": "Close",
-      "description": "Close with a final image and contact path. Leave the prospect with one line about why they're better off acting now than later, and clear instructions for how to engage.",
-      "layout": "title",
-      "instructions": "Logo & contact info",
-      "type": "text"
-    }
-  ]
-}

package/dist/spec/catalogs/narratives/pitch-deck.json

@@ -1,107 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "pitch-deck",
-  "name": "Startup Pitch Deck",
-  "summary": "The canonical investor-pitch arc, drawn from Sequoia and Y Combinator's templates. Optimized for 10–20 minute meetings with VCs and angels. Each beat answers the question an investor will ask next.",
-  "audienceFit": [
-    "investors",
-    "venture-capitalists",
-    "angels",
-    "advisors"
-  ],
-  "duration": {
-    "min": 10,
-    "max": 20
-  },
-  "tags": [
-    "startup",
-    "fundraising",
-    "pitch",
-    "investor"
-  ],
-  "beats": [
-    {
-      "id": "opening",
-      "name": "Opening",
-      "description": "Open with the company name, logo, and a one-line tagline that doubles as a positioning statement. Set the visual tone for the deck. Keep it confident and uncluttered — this is the cover.",
-      "layout": "title"
-    },
-    {
-      "id": "purpose",
-      "name": "Company Purpose",
-      "description": "State in a single sentence what the company does and why it exists. Should be immediately understandable without industry jargon. Often doubles as the answer to 'so what do you do?'"
-    },
-    {
-      "id": "problem",
-      "name": "Problem",
-      "description": "Describe the pain point you solve. Make it concrete with a specific user or customer scenario. The more visceral and recognizable the problem, the stronger the rest of the pitch lands."
-    },
-    {
-      "id": "why-now",
-      "name": "Why Now",
-      "description": "Explain the technological, regulatory, behavioral, or market shift that makes this opportunity possible today and impossible five years ago. Investors want to know why this is a window, not just an idea."
-    },
-    {
-      "id": "market",
-      "name": "Market Size",
-      "description": "Size the opportunity. Top-down (TAM/SAM/SOM) or bottom-up (units × price). Show how big the prize is if you win, and why this market is attractive to a venture-scale outcome."
-    },
-    {
-      "id": "competition",
-      "name": "Competition",
-      "description": "Map the competitive landscape honestly. A 2x2 matrix or feature-comparison grid is fine; what matters is showing you understand the alternatives and where you uniquely fit. Naïve 'no competition' answers tank credibility."
-    },
-    {
-      "id": "solution",
-      "name": "Solution",
-      "description": "Show how you solve the problem and why your approach is uniquely better. Lead with the outcome for the customer, then show the mechanism. This is where you connect problem to product."
-    },
-    {
-      "id": "product",
-      "name": "Product",
-      "description": "Give the product its own moment. Screenshots or a key visual that captures what users actually see and feel. Pick one strong frame over a montage of small ones."
-    },
-    {
-      "id": "demo",
-      "name": "Demo",
-      "description": "Walk through the core user flow end-to-end. Show real software solving a real problem in a real workflow — not a marketing reel. If a live demo is too risky, use a tightly edited recording with narration."
-    },
-    {
-      "id": "traction",
-      "name": "Traction",
-      "description": "Prove momentum with one credible headline metric. Revenue, users, growth rate, customer logos — whatever best shows the business is working. One strong chart beats five vanity numbers."
-    },
-    {
-      "id": "growth",
-      "name": "Growth Drivers",
-      "description": "Show how the headline metric got there and where it's going. Cohorts, retention, expansion, channel mix — whatever explains the engine behind the number. Investors back the trajectory, not the snapshot."
-    },
-    {
-      "id": "business-model",
-      "name": "Business Model",
-      "description": "Explain how the company makes money. Pricing, unit economics, sales motion, payback period. Should answer: what does it cost to acquire a customer, and what do they pay you?"
-    },
-    {
-      "id": "team",
-      "name": "Team",
-      "description": "Establish why this team uniquely wins this market. Founder backgrounds, relevant experience, prior outcomes, key advisors. Investors back people first; make the case."
-    },
-    {
-      "id": "financials",
-      "name": "Financials",
-      "description": "Show the financial picture: historical revenue, burn, runway, and forward projection. Be conservative-but-credible — investors will discount aggressive numbers and reward defensible ones."
-    },
-    {
-      "id": "ask",
-      "name": "The Ask",
-      "description": "State the round size, intended use of funds, and what milestones the capital takes you to. Be specific — investors should leave knowing exactly what you want and what they get.",
-      "layout": "title"
-    },
-    {
-      "id": "closing",
-      "name": "Closing",
-      "description": "Close on a strong final image: logo, contact info, and the one line you most want the investor to remember. Leave space for the conversation that follows.",
-      "layout": "title"
-    }
-  ]
-}

package/dist/spec/catalogs/narratives/problem-solution.json

@@ -1,61 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "problem-solution",
-  "name": "Problem → Solution",
-  "summary": "Classic business arc: name the pain, raise the stakes, present your fix, show how it works, prove it, ask. The default for sales decks, internal proposals, and most general business presentations.",
-  "audienceFit": [
-    "customers",
-    "stakeholders",
-    "executives",
-    "internal-teams"
-  ],
-  "duration": {
-    "min": 5,
-    "max": 30
-  },
-  "tags": [
-    "business",
-    "sales",
-    "general",
-    "proposal"
-  ],
-  "beats": [
-    {
-      "id": "hook",
-      "name": "Hook",
-      "description": "Open with a striking question, statistic, customer quote, or moment that earns the audience's attention. The goal is to make them want to hear what comes next, not to convey information.",
-      "layout": "title"
-    },
-    {
-      "id": "problem",
-      "name": "The Problem",
-      "description": "Name the pain in concrete terms. Make it visceral and specific — describe who hurts, how, and what they're trying to do today that isn't working. Avoid abstractions; use real examples or scenarios the audience recognizes."
-    },
-    {
-      "id": "stakes",
-      "name": "Why It Matters",
-      "description": "Quantify the cost of inaction or the upside of action. Use numbers, trends, customer impact, competitive pressure — whatever makes the audience feel the size of the problem and care about solving it now rather than later."
-    },
-    {
-      "id": "solution",
-      "name": "The Solution",
-      "description": "Reveal your approach and what it produces for the customer. Lead with the outcome, not the architecture. Keep it concrete: what does the audience get, and what changes for them?"
-    },
-    {
-      "id": "mechanism",
-      "name": "How It Works",
-      "description": "Show the moving parts that make the solution credible. Walk through the key mechanism, workflow, or technical insight that explains why this approach succeeds where others have failed. Enough detail to earn trust; not so much that you lose the room."
-    },
-    {
-      "id": "evidence",
-      "name": "Proof",
-      "description": "Demonstrate the solution works. Use customer logos, before/after metrics, demos, case studies, third-party validation — whatever de-risks the claim. One strong piece of proof beats three weak ones."
-    },
-    {
-      "id": "ask",
-      "name": "The Ask",
-      "description": "State a clear, specific call to action. What do you want the audience to do, decide, or commit to next? Make the smallest credible ask that moves things forward, and make it unambiguous.",
-      "layout": "title"
-    }
-  ]
-}

package/dist/spec/catalogs/narratives/product-launch.json

@@ -1,104 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "product-launch",
-  "name": "Product Launch",
-  "summary": "Persuasive launch arc: open with brand, hook with a promise, set the conflict, raise the stakes, reveal the product, raise stakes again, sell, and call to action. Tuned for keynote-style launches and major announcement decks.",
-  "audienceFit": [
-    "customers",
-    "press",
-    "general-audience",
-    "partners"
-  ],
-  "duration": {
-    "min": 15,
-    "max": 45
-  },
-  "tags": [
-    "startup",
-    "launch",
-    "marketing",
-    "keynote"
-  ],
-  "beats": [
-    {
-      "id": "opening",
-      "name": "Opening",
-      "description": "Open with the company brand and a confident visual. Set the tone — this is a moment, not a meeting. One slide that signals the audience is somewhere worth being.",
-      "layout": "title",
-      "instructions": "Show company branding",
-      "type": "text"
-    },
-    {
-      "id": "promise",
-      "name": "Promise",
-      "description": "Hook the audience with the promise of the talk. Tell them, in one sentence, what they're about to see and why it matters to them. Specific promises buy patient audiences.",
-      "instructions": "Hook the audience",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "context",
-      "name": "Context",
-      "description": "Set the stage with the world the product enters. The customer reality, the market state, the unmet expectation. Context turns the launch from a product release into a moment in a larger story.",
-      "instructions": "Set the stage",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "conflict",
-      "name": "Conflict",
-      "description": "Introduce the villain — the problem, friction, or status quo the product opposes. Make the conflict concrete enough that the audience can name a moment they've felt it themselves.",
-      "instructions": "Introduce villain/problem",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "stakes",
-      "name": "Stakes",
-      "description": "Emphasize what's at risk if the conflict isn't resolved. Quantify, personalize, dramatize. Stakes are what convert a curious audience into an invested one.",
-      "instructions": "Emphasize importance",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "reveal",
-      "name": "Reveal",
-      "description": "Showcase the product. One striking visual, one defining capability, one sentence that captures what's new. Earn the applause line; don't bury it under a bullet list.",
-      "instructions": "Showcase the solution",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "raise-stakes",
-      "name": "Raise the Stakes",
-      "description": "Highlight where the alternatives fall short and what they cost the customer. Re-energize the room midway by sharpening the contrast with the reveal.",
-      "instructions": "Highlight shortcomings of alternatives",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "raise-stakes-again",
-      "name": "Reinforce the Need",
-      "description": "Reinforce why change is non-negotiable now. A second beat of stakes, framed differently — perhaps a customer voice or a future cost. Cement the reason to act.",
-      "instructions": "Reinforce the need for change",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "sell",
-      "name": "Sell",
-      "description": "Make the audience want the product. Lead with the outcome it produces in their lives. Pricing, packaging, availability go here, but only after the desire is built.",
-      "instructions": "Make them want your solution",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "cta",
-      "name": "Call to Action",
-      "description": "Close with the single action you want from the audience. Pre-order, sign up, attend, share. Make it simple, specific, and immediate.",
-      "layout": "title",
-      "instructions": "Inspire action",
-      "type": "text"
-    }
-  ]
-}

package/dist/spec/catalogs/narratives/project-proposal.json

@@ -1,104 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "project-proposal",
-  "name": "Project Proposal",
-  "summary": "Internal proposal arc for greenlighting a project: hook, problem, idea, benefits, justification, plan, timeline, risks, outlook, ask. Designed to take a sponsor from 'never heard of this' to 'approved' inside a single meeting.",
-  "audienceFit": [
-    "executives",
-    "sponsors",
-    "managers",
-    "internal-teams"
-  ],
-  "duration": {
-    "min": 15,
-    "max": 45
-  },
-  "tags": [
-    "management",
-    "proposal",
-    "internal",
-    "planning"
-  ],
-  "beats": [
-    {
-      "id": "elevator-pitch",
-      "name": "Elevator Pitch",
-      "description": "Open with the proposal in one slide: the project name, the audience, the goal, and the headline benefit. If a sponsor reads only this slide, they should still know what they're being asked to approve.",
-      "instructions": "Audience hook & objectives",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "problem-statement",
-      "name": "Problem Statement",
-      "description": "Articulate the problem this project solves and why it deserves resources now. Tie it to a known business goal or pain. Vague problems produce vague approvals.",
-      "instructions": "Highlight struggles & project necessity",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "core-concept",
-      "name": "Core Concept",
-      "description": "Describe the central idea of the project in plain language. The 'what' before the 'how.' A reader should be able to repeat the concept in one sentence after this slide.",
-      "instructions": "Share actionable idea",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "benefits",
-      "name": "Benefits",
-      "description": "Quantify the impact: revenue, cost, risk, customer, capability. Use numbers where possible and clear comparisons where not. Each benefit should map to a metric the sponsor cares about.",
-      "instructions": "Spotlight key metrics",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "justification",
-      "name": "Justification",
-      "description": "Connect the project to broader strategy, OKRs, or constraints the audience already cares about. Show why this project is more important than the alternatives competing for the same resources.",
-      "instructions": "Strategic alignment & significance",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "approach",
-      "name": "Approach",
-      "description": "Lay out how the project will be executed: the solution, the team shape, the budget envelope. Enough detail to feel credible, not so much that it pre-commits to choices that will mature in flight.",
-      "instructions": "Solution, resources, & budget",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "timeline",
-      "name": "Timeline",
-      "description": "Show the project phases on a timeline, with major milestones and decision points marked. Sponsors are buying a sequence of bets, not a single launch — make those bets visible.",
-      "instructions": "Outline project phases",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "risks",
-      "name": "Risks",
-      "description": "Name the top risks honestly and pair each with a mitigation or open question. Listing risks without mitigations signals you haven't thought it through; hiding risks signals worse.",
-      "instructions": "Consider potential challenges",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "outlook",
-      "name": "Outlook",
-      "description": "Paint the picture of what the organization looks like a quarter or year after the project ships. Stretch beyond the immediate deliverable to the second-order benefits.",
-      "instructions": "Envision project impact",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "wrap-up",
-      "name": "Wrap Up",
-      "description": "Recap the proposal and state the specific decision you're asking for: approval, budget, headcount, sponsorship. Make it easy to say yes today.",
-      "layout": "title",
-      "instructions": "Summarize & persuade",
-      "type": "text"
-    }
-  ]
-}

package/dist/spec/catalogs/narratives/pyramid-principle.json

@@ -1,48 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "pyramid-principle",
-  "name": "Pyramid Principle",
-  "summary": "Lead with your conclusion, then provide supporting logic. Respects audience time and attention.",
-  "description": "Lead with the conclusion, then provide the supporting logic. State the main recommendation up front, follow with three or four arguments that support it, then back each argument with data and examples. The tone is deductive: conclusion first, reasoning second, so the audience never waits for the point. Best for executive presentations, recommendations, and time-constrained settings; typical decks run 3-8 slides (consulting recommendation, investment thesis, strategic options analysis).",
-  "audienceFit": [
-    "executive",
-    "board",
-    "time-pressed-decision-makers"
-  ],
-  "duration": {
-    "min": 5,
-    "max": 20
-  },
-  "tags": [
-    "executive",
-    "strategy",
-    "deductive",
-    "recommendation"
-  ],
-  "beats": [
-    {
-      "id": "answer-first",
-      "name": "Answer First",
-      "description": "Lead with your main point or recommendation. Don't make executives wait for it.",
-      "instructions": "Lead with the conclusion or recommendation.",
-      "type": "text",
-      "layout": "title"
-    },
-    {
-      "id": "key-arguments",
-      "name": "Key Arguments",
-      "description": "Provide 3-4 supporting reasons that logically support your answer.",
-      "instructions": "Group the main reasons supporting the answer.",
-      "type": "text",
-      "layout": "text-3x"
-    },
-    {
-      "id": "supporting-evidence",
-      "name": "Supporting Evidence",
-      "description": "Back each argument with data, examples, or proof points.",
-      "instructions": "Back each argument with verifiable proof.",
-      "type": "chart",
-      "layout": "chart-1x"
-    }
-  ]
-}

package/dist/spec/catalogs/narratives/qbr.json

@@ -1,85 +0,0 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "qbr",
-  "name": "Quarterly Business Review",
-  "summary": "Standard QBR / business-review arc for internal leadership reviews. Recap commitments, show what the numbers say, separate wins from challenges, lay out the plan, surface risks, and request the asks the team needs to execute.",
-  "audienceFit": [
-    "leadership",
-    "executives",
-    "cross-functional-partners"
-  ],
-  "duration": {
-    "min": 30,
-    "max": 90
-  },
-  "tags": [
-    "internal",
-    "review",
-    "operations",
-    "reporting"
-  ],
-  "beats": [
-    {
-      "id": "objectives",
-      "name": "Objectives",
-      "description": "Open with what this review is for and what decisions you want out of it. Frame the scope and the hour ahead, so the audience knows what they're being asked to weigh in on.",
-      "layout": "title",
-      "instructions": "Set the expectations",
-      "type": "text"
-    },
-    {
-      "id": "recap",
-      "name": "Recap",
-      "description": "Briefly remind the audience what the team committed to last quarter and the high-level results against those commitments. Keep it terse — this grounds the review in prior context, but the meat is ahead."
-    },
-    {
-      "id": "performance-headline",
-      "name": "Performance Headline",
-      "description": "Show the top three to five KPIs with target vs actual and direction-of-travel. One slide that lets a busy executive grasp the quarter's outcome at a glance. Lead with the number, not the methodology."
-    },
-    {
-      "id": "performance-detail",
-      "name": "Performance Detail",
-      "description": "Drill into the supporting metrics by area or function. One chart per metric; clear y-axis, clear unit, clear comparison period. Call out anomalies before someone else does."
-    },
-    {
-      "id": "wins",
-      "name": "Wins",
-      "description": "Highlight the quarter's biggest wins and who drove them. Be specific — name the deal, the launch, the customer, the team. Recognition belongs in the deck, not just in the meeting."
-    },
-    {
-      "id": "challenges",
-      "name": "Challenges",
-      "description": "Name the misses and headwinds honestly. What didn't work, what's still hard, what got harder. Pretending things are fine costs more credibility than acknowledging they aren't.",
-      "instructions": "Address difficulties",
-      "type": "text",
-      "layout": "text-1x"
-    },
-    {
-      "id": "insights",
-      "name": "Insights",
-      "description": "Translate the numbers into 'so what.' What did the data tell you about customers, the market, your operations, your bets? Insights should be opinions backed by evidence, not restatements of the metrics."
-    },
-    {
-      "id": "priorities",
-      "name": "Next-Quarter Priorities",
-      "description": "Lay out the next quarter's top priorities. Each should trace clearly back to an insight or commitment. Three to five priorities, max — laundry lists are a tell that the team hasn't decided what matters most."
-    },
-    {
-      "id": "sequencing",
-      "name": "Sequencing",
-      "description": "Show the order in which priorities ship and how they fit together. Dependencies, milestones, target dates. The audience should leave able to predict what comes when, not just what."
-    },
-    {
-      "id": "risks",
-      "name": "Risks",
-      "description": "Name the risks to the plan honestly. Dependencies, assumptions, capacity gaps, market factors. For each risk, state the mitigation or the open question the audience can help resolve."
-    },
-    {
-      "id": "asks",
-      "name": "Asks",
-      "description": "Specific, named requests of the audience. Decisions needed, resources required, escalations to unblock. End with clarity on what happens next and who owns it.",
-      "layout": "title"
-    }
-  ]
-}