@openpresentation/opf 0.1.0 → 0.2.2

package/dist/spec/catalogs/narratives/business-review.json

@@ -1,119 +1,119 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "business-review",
-  "name": "Business Review",
-  "summary": "Full-loop review of recent activities to identify achievements, address challenges, and plan improvements. Goes deeper than a status update — closer to a customer-facing or partner-facing relationship review.",
-  "audienceFit": [
-    "customers",
-    "partners",
-    "stakeholders",
-    "leadership"
-  ],
-  "durationRange": {
-    "minMinutes": 30,
-    "maxMinutes": 90
-  },
-  "tags": [
-    "customer-relationship",
-    "review",
-    "operations"
-  ],
-  "beats": [
-    {
-      "id": "logo",
-      "name": "Logo",
-      "description": "Cover slide with logos and the review period. Establishes brand identity and signals the level of formality the rest of the deck will hold to.",
-      "layoutHint": "title-left",
-      "instructions": "Identity & representation",
-      "slideType": "text"
-    },
-    {
-      "id": "opening",
-      "name": "Opening",
-      "description": "Frame the meeting context and the goals for the next hour. What you'll cover, what decisions you want, what you don't intend to relitigate.",
-      "instructions": "Meeting context & goals",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "review",
-      "name": "Review",
-      "description": "Outline the recent activities in scope: launches, projects, programs. Just enough scope-setting that the rest of the deck has shared vocabulary.",
-      "instructions": "Outline recent activities",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "successes",
-      "name": "Successes",
-      "description": "Recognize the achievements in the review window. Lead with outcomes the audience cares about, not effort. Specific moves earn more credibility than aggregate progress.",
-      "instructions": "Recognize achievements",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "challenges",
-      "name": "Challenges",
-      "description": "Address the problems faced honestly. What didn't work, what's still hard. Naming challenges in front of the audience earns more trust than letting them ask.",
-      "instructions": "Address problems faced",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "solutions",
-      "name": "Solutions",
-      "description": "Discuss the fixes already implemented. Pair each with the result it produced, or, if it's still in flight, with the leading indicator you're watching.",
-      "instructions": "Discuss implemented fixes",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "outcome",
-      "name": "Outcome",
-      "description": "Display the results achieved across the review window. Let the data carry the slide; supporting commentary should explain context, not inflate the numbers.",
-      "instructions": "Display results achieved",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "insights",
-      "name": "Insights",
-      "description": "Highlight the key learnings. What was confirmed, what surprised you, what the audience should take away. Insights are the slides people quote in follow-on meetings.",
-      "instructions": "Highlight key learnings",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "future-strategy",
-      "name": "Future Strategy",
-      "description": "Define the next steps and the strategic direction that follows from the review. Specific enough to sequence; flexible enough to adapt.",
-      "instructions": "Define next steps",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "feedback",
-      "name": "Feedback",
-      "description": "Capture audience thoughts. Two or three explicit prompts where you want input or alignment. The strength of a relationship review is in the conversation it provokes.",
-      "instructions": "Capture audience thoughts",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "next-review",
-      "name": "Next Review",
-      "description": "Plan for follow-up: when the next review happens, what evidence you'll bring, what decisions are deferred until then. Continuity is the point of the cadence.",
-      "instructions": "Plan for follow-up",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "closing",
-      "name": "Closing",
-      "description": "Recap and express optimism about the path forward. Close with the next concrete step and the people responsible for it.",
-      "layoutHint": "title-left",
-      "instructions": "Recap and express optimism",
-      "slideType": "text"
-    }
-  ]
-}
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "business-review",
+  "name": "Business Review",
+  "summary": "Full-loop review of recent activities to identify achievements, address challenges, and plan improvements. Goes deeper than a status update — closer to a customer-facing or partner-facing relationship review.",
+  "audienceFit": [
+    "customers",
+    "partners",
+    "stakeholders",
+    "leadership"
+  ],
+  "durationRange": {
+    "minMinutes": 30,
+    "maxMinutes": 90
+  },
+  "tags": [
+    "customer-relationship",
+    "review",
+    "operations"
+  ],
+  "beats": [
+    {
+      "id": "logo",
+      "name": "Logo",
+      "description": "Cover slide with logos and the review period. Establishes brand identity and signals the level of formality the rest of the deck will hold to.",
+      "layoutHint": "title-left",
+      "instructions": "Identity & representation",
+      "slideType": "text"
+    },
+    {
+      "id": "opening",
+      "name": "Opening",
+      "description": "Frame the meeting context and the goals for the next hour. What you'll cover, what decisions you want, what you don't intend to relitigate.",
+      "instructions": "Meeting context & goals",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "review",
+      "name": "Review",
+      "description": "Outline the recent activities in scope: launches, projects, programs. Just enough scope-setting that the rest of the deck has shared vocabulary.",
+      "instructions": "Outline recent activities",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "successes",
+      "name": "Successes",
+      "description": "Recognize the achievements in the review window. Lead with outcomes the audience cares about, not effort. Specific moves earn more credibility than aggregate progress.",
+      "instructions": "Recognize achievements",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "challenges",
+      "name": "Challenges",
+      "description": "Address the problems faced honestly. What didn't work, what's still hard. Naming challenges in front of the audience earns more trust than letting them ask.",
+      "instructions": "Address problems faced",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "solutions",
+      "name": "Solutions",
+      "description": "Discuss the fixes already implemented. Pair each with the result it produced, or, if it's still in flight, with the leading indicator you're watching.",
+      "instructions": "Discuss implemented fixes",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "outcome",
+      "name": "Outcome",
+      "description": "Display the results achieved across the review window. Let the data carry the slide; supporting commentary should explain context, not inflate the numbers.",
+      "instructions": "Display results achieved",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "insights",
+      "name": "Insights",
+      "description": "Highlight the key learnings. What was confirmed, what surprised you, what the audience should take away. Insights are the slides people quote in follow-on meetings.",
+      "instructions": "Highlight key learnings",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "future-strategy",
+      "name": "Future Strategy",
+      "description": "Define the next steps and the strategic direction that follows from the review. Specific enough to sequence; flexible enough to adapt.",
+      "instructions": "Define next steps",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "feedback",
+      "name": "Feedback",
+      "description": "Capture audience thoughts. Two or three explicit prompts where you want input or alignment. The strength of a relationship review is in the conversation it provokes.",
+      "instructions": "Capture audience thoughts",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "next-review",
+      "name": "Next Review",
+      "description": "Plan for follow-up: when the next review happens, what evidence you'll bring, what decisions are deferred until then. Continuity is the point of the cadence.",
+      "instructions": "Plan for follow-up",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "closing",
+      "name": "Closing",
+      "description": "Recap and express optimism about the path forward. Close with the next concrete step and the people responsible for it.",
+      "layoutHint": "title-left",
+      "instructions": "Recap and express optimism",
+      "slideType": "text"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/capacity-planning.json

@@ -1,88 +1,88 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "capacity-planning",
-  "name": "Capacity Planning",
-  "summary": "Workforce and operational capacity-planning arc: kickoff, urgency, current state, projection, tactics, implementation, revision, conclusion. For decks where leadership must decide whether the organization has enough resources to meet upcoming demand.",
-  "audienceFit": [
-    "leadership",
-    "operations",
-    "hr-partners",
-    "finance"
-  ],
-  "durationRange": {
-    "minMinutes": 20,
-    "maxMinutes": 45
-  },
-  "tags": [
-    "workforce",
-    "operations",
-    "planning",
-    "resource-management"
-  ],
-  "beats": [
-    {
-      "id": "kickoff",
-      "name": "Kickoff",
-      "description": "Introduce what the planning exercise covers and the decision you need from the audience. Frame the time horizon and the resources in scope so the rest of the deck stays bounded.",
-      "layoutHint": "title-center",
-      "instructions": "Introduce the topic",
-      "slideType": "text"
-    },
-    {
-      "id": "urgency",
-      "name": "Urgency",
-      "description": "Show why this is the right moment to plan capacity. Pipeline shifts, hiring freezes, operational stress signals. Urgency turns capacity from an annual ritual into a decision the audience leans into.",
-      "instructions": "Show needs",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "situation",
-      "name": "Situation",
-      "description": "Highlight the current resource picture: people, tools, infrastructure, vendor capacity. Show utilization, not just headcount. The audience should know where slack and stress live today.",
-      "instructions": "Highlight current resources",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "projection",
-      "name": "Projection",
-      "description": "Predict future demand under your base case and a sensitivity case. Tie demand to specific drivers — pipeline, launches, seasonality — so the audience can challenge the assumptions, not just the totals.",
-      "instructions": "Predict future demands",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "tactics",
-      "name": "Tactics",
-      "description": "Suggest the strategies for closing any gap: hiring, automation, outsourcing, prioritization. Each tactic should map to a specific demand driver and a defensible cost.",
-      "instructions": "Suggest coping strategies",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "implementation",
-      "name": "Implementation",
-      "description": "Discuss how the plan gets deployed. Sequencing, owners, dependencies, lead times. Capacity decisions slip the most when the rollout isn't planned with the same rigor as the sizing.",
-      "instructions": "Discuss deployment plans",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "revision",
-      "name": "Revision",
-      "description": "Define the leading indicators that would trigger a re-plan, and the cadence of review. Capacity plans age fast; show the audience how the plan stays alive.",
-      "instructions": "Evaluate and adjust",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "conclusion",
-      "name": "Conclusion",
-      "description": "Wrap up with the specific recommendations and the decisions you need today. End with the next checkpoint and what evidence will be on the table at it.",
-      "layoutHint": "title-left",
-      "instructions": "Wrap-up & recommendations",
-      "slideType": "text"
-    }
-  ]
-}
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "capacity-planning",
+  "name": "Capacity Planning",
+  "summary": "Workforce and operational capacity-planning arc: kickoff, urgency, current state, projection, tactics, implementation, revision, conclusion. For decks where leadership must decide whether the organization has enough resources to meet upcoming demand.",
+  "audienceFit": [
+    "leadership",
+    "operations",
+    "hr-partners",
+    "finance"
+  ],
+  "durationRange": {
+    "minMinutes": 20,
+    "maxMinutes": 45
+  },
+  "tags": [
+    "workforce",
+    "operations",
+    "planning",
+    "resource-management"
+  ],
+  "beats": [
+    {
+      "id": "kickoff",
+      "name": "Kickoff",
+      "description": "Introduce what the planning exercise covers and the decision you need from the audience. Frame the time horizon and the resources in scope so the rest of the deck stays bounded.",
+      "layoutHint": "title-center",
+      "instructions": "Introduce the topic",
+      "slideType": "text"
+    },
+    {
+      "id": "urgency",
+      "name": "Urgency",
+      "description": "Show why this is the right moment to plan capacity. Pipeline shifts, hiring freezes, operational stress signals. Urgency turns capacity from an annual ritual into a decision the audience leans into.",
+      "instructions": "Show needs",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "situation",
+      "name": "Situation",
+      "description": "Highlight the current resource picture: people, tools, infrastructure, vendor capacity. Show utilization, not just headcount. The audience should know where slack and stress live today.",
+      "instructions": "Highlight current resources",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "projection",
+      "name": "Projection",
+      "description": "Predict future demand under your base case and a sensitivity case. Tie demand to specific drivers — pipeline, launches, seasonality — so the audience can challenge the assumptions, not just the totals.",
+      "instructions": "Predict future demands",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "tactics",
+      "name": "Tactics",
+      "description": "Suggest the strategies for closing any gap: hiring, automation, outsourcing, prioritization. Each tactic should map to a specific demand driver and a defensible cost.",
+      "instructions": "Suggest coping strategies",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "implementation",
+      "name": "Implementation",
+      "description": "Discuss how the plan gets deployed. Sequencing, owners, dependencies, lead times. Capacity decisions slip the most when the rollout isn't planned with the same rigor as the sizing.",
+      "instructions": "Discuss deployment plans",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "revision",
+      "name": "Revision",
+      "description": "Define the leading indicators that would trigger a re-plan, and the cadence of review. Capacity plans age fast; show the audience how the plan stays alive.",
+      "instructions": "Evaluate and adjust",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "conclusion",
+      "name": "Conclusion",
+      "description": "Wrap up with the specific recommendations and the decisions you need today. End with the next checkpoint and what evidence will be on the table at it.",
+      "layoutHint": "title-left",
+      "instructions": "Wrap-up & recommendations",
+      "slideType": "text"
+    }
+  ]
+}

package/dist/spec/catalogs/narratives/challenge-resolution.json

@@ -1,80 +1,80 @@
-{
-  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
-  "id": "challenge-resolution",
-  "name": "Challenge → Resolution",
-  "summary": "Identify a current business challenge, trace its origins, and recommend an actionable resolution. Useful for management consulting, internal strategy memos, and any deck where the audience needs a clear path from problem to plan.",
-  "audienceFit": [
-    "executives",
-    "managers",
-    "stakeholders",
-    "internal-teams"
-  ],
-  "durationRange": {
-    "minMinutes": 10,
-    "maxMinutes": 30
-  },
-  "tags": [
-    "management",
-    "strategy",
-    "consulting",
-    "advisory"
-  ],
-  "beats": [
-    {
-      "id": "hook",
-      "name": "Hook",
-      "description": "Open with a specific, visible signal of the challenge — a metric heading the wrong way, a customer story, a competitive event. The hook should make the audience nod that yes, this matters.",
-      "instructions": "Capture audience attention",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "dilemma",
-      "name": "Dilemma",
-      "description": "State the challenge plainly. What is failing, who is feeling it, and why has it now risen to a level that demands a decision? The dilemma must feel real, not academic.",
-      "instructions": "Present the problem",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "backdrop",
-      "name": "Backdrop",
-      "description": "Provide the context behind the dilemma: how it formed, what's been tried, what constraints exist. Just enough history that the audience trusts your diagnosis without drowning in detail.",
-      "instructions": "Provide context",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "remedy",
-      "name": "Remedy",
-      "description": "Propose the resolution. Lead with the recommendation, then sketch the approach. Be opinionated — vague remedies invite vague responses.",
-      "instructions": "Propose a solution",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "evidence",
-      "name": "Evidence",
-      "description": "Demonstrate why the remedy will work. Comparable cases, supporting data, or pilot results. Choose evidence that addresses the audience's most likely objection, not the one easiest to answer.",
-      "instructions": "Demonstrate success",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "motivate",
-      "name": "Motivate",
-      "description": "Make the case for acting now. Quantify the cost of delay and the upside of decisive action. Help the audience picture the room a quarter from now if they say yes.",
-      "instructions": "Encourage action",
-      "slideType": "text",
-      "layoutHint": "text-1x-left"
-    },
-    {
-      "id": "conclusion",
-      "name": "Conclusion",
-      "description": "Recap the challenge, the remedy, and the specific decision you need from the audience. End with a clear ask, not a summary slide.",
-      "layoutHint": "title-left",
-      "instructions": "Recap and end powerfully",
-      "slideType": "text"
-    }
-  ]
-}
+{
+  "$schema": "https://openpresentation.org/schema/opf-narrative/v1",
+  "id": "challenge-resolution",
+  "name": "Challenge → Resolution",
+  "summary": "Identify a current business challenge, trace its origins, and recommend an actionable resolution. Useful for management consulting, internal strategy memos, and any deck where the audience needs a clear path from problem to plan.",
+  "audienceFit": [
+    "executives",
+    "managers",
+    "stakeholders",
+    "internal-teams"
+  ],
+  "durationRange": {
+    "minMinutes": 10,
+    "maxMinutes": 30
+  },
+  "tags": [
+    "management",
+    "strategy",
+    "consulting",
+    "advisory"
+  ],
+  "beats": [
+    {
+      "id": "hook",
+      "name": "Hook",
+      "description": "Open with a specific, visible signal of the challenge — a metric heading the wrong way, a customer story, a competitive event. The hook should make the audience nod that yes, this matters.",
+      "instructions": "Capture audience attention",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "dilemma",
+      "name": "Dilemma",
+      "description": "State the challenge plainly. What is failing, who is feeling it, and why has it now risen to a level that demands a decision? The dilemma must feel real, not academic.",
+      "instructions": "Present the problem",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "backdrop",
+      "name": "Backdrop",
+      "description": "Provide the context behind the dilemma: how it formed, what's been tried, what constraints exist. Just enough history that the audience trusts your diagnosis without drowning in detail.",
+      "instructions": "Provide context",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "remedy",
+      "name": "Remedy",
+      "description": "Propose the resolution. Lead with the recommendation, then sketch the approach. Be opinionated — vague remedies invite vague responses.",
+      "instructions": "Propose a solution",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "evidence",
+      "name": "Evidence",
+      "description": "Demonstrate why the remedy will work. Comparable cases, supporting data, or pilot results. Choose evidence that addresses the audience's most likely objection, not the one easiest to answer.",
+      "instructions": "Demonstrate success",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "motivate",
+      "name": "Motivate",
+      "description": "Make the case for acting now. Quantify the cost of delay and the upside of decisive action. Help the audience picture the room a quarter from now if they say yes.",
+      "instructions": "Encourage action",
+      "slideType": "text",
+      "layoutHint": "text-1x-left"
+    },
+    {
+      "id": "conclusion",
+      "name": "Conclusion",
+      "description": "Recap the challenge, the remedy, and the specific decision you need from the audience. End with a clear ask, not a summary slide.",
+      "layoutHint": "title-left",
+      "instructions": "Recap and end powerfully",
+      "slideType": "text"
+    }
+  ]
+}