@openpresentation/opf 0.1.0 → 0.2.1

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

@@ -1,104 +1,104 @@
-{
-  "$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"
-  ],
-  "durationRange": {
-    "minMinutes": 15,
-    "maxMinutes": 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.",
-      "layoutHint": "title-left",
-      "instructions": "Show company branding",
-      "slideType": "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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.",
-      "layoutHint": "title-left",
-      "instructions": "Inspire action",
-      "slideType": "text"
-    }
-  ]
-}
+{
+  "$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"
+  ],
+  "durationRange": {
+    "minMinutes": 15,
+    "maxMinutes": 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.",
+      "layoutHint": "title-left",
+      "instructions": "Show company branding",
+      "slideType": "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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.",
+      "layoutHint": "title-left",
+      "instructions": "Inspire action",
+      "slideType": "text"
+    }
+  ]
+}

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

@@ -1,104 +1,104 @@
-{
-  "$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"
-  ],
-  "durationRange": {
-    "minMinutes": 15,
-    "maxMinutes": 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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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.",
-      "layoutHint": "title-left",
-      "instructions": "Summarize & persuade",
-      "slideType": "text"
-    }
-  ]
-}
+{
+  "$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"
+  ],
+  "durationRange": {
+    "minMinutes": 15,
+    "maxMinutes": 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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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.",
+      "layoutHint": "title-left",
+      "instructions": "Summarize & persuade",
+      "slideType": "text"
+    }
+  ]
+}

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

@@ -1,85 +1,85 @@
-{
-  "$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"
-  ],
-  "durationRange": {
-    "minMinutes": 30,
-    "maxMinutes": 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.",
-      "layoutHint": "title-center",
-      "instructions": "Set the expectations",
-      "slideType": "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",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "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.",
-      "layoutHint": "title-left"
-    }
-  ]
-}
+{
+  "$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"
+  ],
+  "durationRange": {
+    "minMinutes": 30,
+    "maxMinutes": 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.",
+      "layoutHint": "title-center",
+      "instructions": "Set the expectations",
+      "slideType": "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",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "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.",
+      "layoutHint": "title-left"
+    }
+  ]
+}