@exaudeus/workrail 3.13.0 → 3.15.0

package/workflows/presentation-creation.json

@@ -1,165 +1,165 @@
 {
-    "id": "presentation-creation",
-    "name": "Presentation Creation Workflow",
-    "version": "1.0.0",
-    "description": "Guides you through creating a compelling, audience-grounded presentation. Covers audience analysis, content strategy, slide structure, content development, and delivery preparation. Tool-agnostic: output works with PowerPoint, Google Slides, Keynote, or any other presentation tool.",
-    "preconditions": [
-        "You have a clear presentation topic or objective.",
-        "You know roughly who your audience is.",
-        "You have access to any source materials or data you plan to reference."
-    ],
-    "clarificationPrompts": [
-        "What is the main objective or key message of your presentation?",
-        "Who is your target audience and what is their professional context?"
-    ],
-    "metaGuidance": [
-        "Ground every decision in your audience profile. Generic presentations fail because they are not written for anyone specific.",
-        "Each step should explicitly reference outputs from the previous step to avoid boilerplate drift.",
-        "Prioritize clarity over completeness. A tight presentation that lands one message beats a comprehensive one that loses the audience.",
-        "Build in engagement moments throughout, not just at the opening.",
-        "Every section should pass the 'so what?' test: if the audience cannot articulate why they should care, cut or reframe.",
-        "Always have a clear call-to-action. Tell the audience what you want them to do or believe after your presentation.",
-        "Test all technical elements well before your presentation day.",
-        "Prepare contingency plans for common problems: technology failures, timing overruns, tough questions."
-    ],
-    "steps": [
-        {
-            "id": "audience-and-context-analysis",
-            "title": "Audience & Context Analysis",
-            "promptBlocks": {
-                "goal": "Build a concrete audience profile and context map that every downstream step will rely on. Shallow audience analysis is the root cause of generic presentations.",
-                "constraints": [
-                    "Be specific, not categorical. 'Senior engineers at a fintech startup' is useful; 'technical professionals' is not.",
-                    "Address both explicit needs (what they asked for) and implicit needs (what they actually need to hear).",
-                    "Consider the broader context: what happens before and after your presentation? What mood will the audience be in?"
-                ],
-                "procedure": [
-                    "Define the audience: professional background, expertise level, role and seniority mix, and any relevant cultural or organizational context.",
-                    "Identify audience motivations: what do they want to learn or decide? What pain points or pressures are they carrying into the room?",
-                    "Analyze the presentation context: event type (conference, internal meeting, client pitch, webinar), setting (in-person, remote, hybrid), time constraints, and follow-up expectations.",
-                    "Define success: what does a successful outcome look like for both you and the audience? What specific action or belief shift are you aiming for?",
-                    "Identify risks: what might cause the audience to disengage, push back, or leave confused?"
-                ],
-                "outputRequired": {
-                    "audienceProfile": "A concise profile covering: demographics and expertise, motivations and pain points, context and setting, success definition, and key engagement risks."
-                },
-                "verify": [
-                    "Does every section contain specific, actionable detail rather than generic categories?",
-                    "Could you use this profile to make a real content decision right now?"
-                ]
-            },
-            "requireConfirmation": true
+  "id": "presentation-creation",
+  "name": "Presentation Creation Workflow",
+  "version": "1.0.0",
+  "description": "Use this to create a compelling presentation. Covers audience analysis, content strategy, slide structure, and delivery preparation. Output works with any presentation tool.",
+  "preconditions": [
+    "You have a clear presentation topic or objective.",
+    "You know roughly who your audience is.",
+    "You have access to any source materials or data you plan to reference."
+  ],
+  "clarificationPrompts": [
+    "What is the main objective or key message of your presentation?",
+    "Who is your target audience and what is their professional context?"
+  ],
+  "metaGuidance": [
+    "Ground every decision in your audience profile. Generic presentations fail because they are not written for anyone specific.",
+    "Each step should explicitly reference outputs from the previous step to avoid boilerplate drift.",
+    "Prioritize clarity over completeness. A tight presentation that lands one message beats a comprehensive one that loses the audience.",
+    "Build in engagement moments throughout, not just at the opening.",
+    "Every section should pass the 'so what?' test: if the audience cannot articulate why they should care, cut or reframe.",
+    "Always have a clear call-to-action. Tell the audience what you want them to do or believe after your presentation.",
+    "Test all technical elements well before your presentation day.",
+    "Prepare contingency plans for common problems: technology failures, timing overruns, tough questions."
+  ],
+  "steps": [
+    {
+      "id": "audience-and-context-analysis",
+      "title": "Audience & Context Analysis",
+      "promptBlocks": {
+        "goal": "Build a concrete audience profile and context map that every downstream step will rely on. Shallow audience analysis is the root cause of generic presentations.",
+        "constraints": [
+          "Be specific, not categorical. 'Senior engineers at a fintech startup' is useful; 'technical professionals' is not.",
+          "Address both explicit needs (what they asked for) and implicit needs (what they actually need to hear).",
+          "Consider the broader context: what happens before and after your presentation? What mood will the audience be in?"
+        ],
+        "procedure": [
+          "Define the audience: professional background, expertise level, role and seniority mix, and any relevant cultural or organizational context.",
+          "Identify audience motivations: what do they want to learn or decide? What pain points or pressures are they carrying into the room?",
+          "Analyze the presentation context: event type (conference, internal meeting, client pitch, webinar), setting (in-person, remote, hybrid), time constraints, and follow-up expectations.",
+          "Define success: what does a successful outcome look like for both you and the audience? What specific action or belief shift are you aiming for?",
+          "Identify risks: what might cause the audience to disengage, push back, or leave confused?"
+        ],
+        "outputRequired": {
+          "audienceProfile": "A concise profile covering: demographics and expertise, motivations and pain points, context and setting, success definition, and key engagement risks."
         },
-        {
-            "id": "content-strategy",
-            "title": "Content Strategy",
-            "promptBlocks": {
-                "goal": "Define the core message and argument structure that will guide every slide and talking point. Using your audience profile from the previous step, build a content strategy grounded in their specific needs.",
-                "constraints": [
-                    "Start with one core message — a single, memorable sentence. Everything else should support it.",
-                    "Supporting arguments should directly address the audience motivations and pain points you identified.",
-                    "The narrative arc should feel natural for this audience in this context — not a generic template unless it actually fits."
-                ],
-                "procedure": [
-                    "State your core message: one clear, memorable sentence that captures the single most important thing you want the audience to take away.",
-                    "Define 3-5 supporting arguments that reinforce your core message. For each, identify the key evidence, example, or story you will use.",
-                    "Design the narrative arc: how will you take the audience from where they are now to where you want them to be? Map the logical and emotional journey.",
-                    "Plan your engagement hooks: surprising statistics, thought-provoking questions, or moments of genuine interaction that break up information delivery.",
-                    "Define your call-to-action: what specific thing do you want the audience to do, believe, or decide after your presentation?"
-                ],
-                "outputRequired": {
-                    "contentStrategy": "Core message (one sentence), supporting arguments with evidence, narrative arc description, engagement hooks, and call-to-action."
-                },
-                "verify": [
-                    "Does every supporting argument trace back to a specific audience need from your audience profile?",
-                    "Does the narrative arc feel designed for this audience, or does it feel like a template?"
-                ]
-            },
-            "requireConfirmation": false
+        "verify": [
+          "Does every section contain specific, actionable detail rather than generic categories?",
+          "Could you use this profile to make a real content decision right now?"
+        ]
+      },
+      "requireConfirmation": true
+    },
+    {
+      "id": "content-strategy",
+      "title": "Content Strategy",
+      "promptBlocks": {
+        "goal": "Define the core message and argument structure that will guide every slide and talking point. Using your audience profile from the previous step, build a content strategy grounded in their specific needs.",
+        "constraints": [
+          "Start with one core message \u2014 a single, memorable sentence. Everything else should support it.",
+          "Supporting arguments should directly address the audience motivations and pain points you identified.",
+          "The narrative arc should feel natural for this audience in this context \u2014 not a generic template unless it actually fits."
+        ],
+        "procedure": [
+          "State your core message: one clear, memorable sentence that captures the single most important thing you want the audience to take away.",
+          "Define 3-5 supporting arguments that reinforce your core message. For each, identify the key evidence, example, or story you will use.",
+          "Design the narrative arc: how will you take the audience from where they are now to where you want them to be? Map the logical and emotional journey.",
+          "Plan your engagement hooks: surprising statistics, thought-provoking questions, or moments of genuine interaction that break up information delivery.",
+          "Define your call-to-action: what specific thing do you want the audience to do, believe, or decide after your presentation?"
+        ],
+        "outputRequired": {
+          "contentStrategy": "Core message (one sentence), supporting arguments with evidence, narrative arc description, engagement hooks, and call-to-action."
         },
-        {
-            "id": "slide-structure",
-            "title": "Slide Structure & Flow",
-            "promptBlocks": {
-                "goal": "Turn your content strategy into a numbered slide outline with clear purpose, content type, and rough timing for each slide. This becomes the blueprint for content development.",
-                "constraints": [
-                    "One key idea per slide. If a slide is trying to say two things, split it.",
-                    "Plan for pacing: balance information-dense slides with breathing room and interaction moments.",
-                    "Think about how the slides will work if someone reads them later without you — titles should be informative, not just labels."
-                ],
-                "procedure": [
-                    "Opening (1-3 slides): attention-grabbing hook, context framing, and agenda or roadmap.",
-                    "Core content blocks: group your supporting arguments into logical sections. For each slide, specify: title, main content type (bullets, chart, image, diagram, quote), and whether it has an interaction moment.",
-                    "Transitions between major sections: a single bridging slide that signals the shift and re-grounds the audience.",
-                    "Closing (2-3 slides): synthesis of core message, call-to-action, next steps or contact information.",
-                    "For each slide, add an estimated time in minutes and mark which slides need significant visual design work."
-                ],
-                "outputRequired": {
-                    "slideOutline": "A numbered slide outline. Each entry: slide number, title, content type, estimated time, and any special notes."
-                },
-                "verify": [
-                    "Does the outline tell a coherent story from opening to close?",
-                    "Does the pacing feel right for the stated time budget?",
-                    "Is there at least one engagement moment in the first third of the presentation?"
-                ]
-            },
-            "requireConfirmation": true
+        "verify": [
+          "Does every supporting argument trace back to a specific audience need from your audience profile?",
+          "Does the narrative arc feel designed for this audience, or does it feel like a template?"
+        ]
+      },
+      "requireConfirmation": false
+    },
+    {
+      "id": "slide-structure",
+      "title": "Slide Structure & Flow",
+      "promptBlocks": {
+        "goal": "Turn your content strategy into a numbered slide outline with clear purpose, content type, and rough timing for each slide. This becomes the blueprint for content development.",
+        "constraints": [
+          "One key idea per slide. If a slide is trying to say two things, split it.",
+          "Plan for pacing: balance information-dense slides with breathing room and interaction moments.",
+          "Think about how the slides will work if someone reads them later without you \u2014 titles should be informative, not just labels."
+        ],
+        "procedure": [
+          "Opening (1-3 slides): attention-grabbing hook, context framing, and agenda or roadmap.",
+          "Core content blocks: group your supporting arguments into logical sections. For each slide, specify: title, main content type (bullets, chart, image, diagram, quote), and whether it has an interaction moment.",
+          "Transitions between major sections: a single bridging slide that signals the shift and re-grounds the audience.",
+          "Closing (2-3 slides): synthesis of core message, call-to-action, next steps or contact information.",
+          "For each slide, add an estimated time in minutes and mark which slides need significant visual design work."
+        ],
+        "outputRequired": {
+          "slideOutline": "A numbered slide outline. Each entry: slide number, title, content type, estimated time, and any special notes."
         },
-        {
-            "id": "content-development",
-            "title": "Content Development",
-            "promptBlocks": {
-                "goal": "Write the actual presentation content — slide text and speaker notes — following the approved outline. Every piece of content should be grounded in your audience profile and core message.",
-                "constraints": [
-                    "Write for the ear, not the eye. Slide text should be sparse; speaker notes should sound natural when spoken aloud.",
-                    "Use active voice and concrete language. Replace abstractions with specific examples.",
-                    "Prepare backup content for questions or extended time: 2-3 extra slides that can be shown if needed."
-                ],
-                "procedure": [
-                    "For each slide in your outline, write the visible slide content: headline, key bullets or visual description, and any data or quotes.",
-                    "Write speaker notes for each slide: talking points, transitions to the next slide, and timing cues.",
-                    "Develop your key stories and examples in full: the narrative, the specific detail that makes it vivid, and the connection back to your core message.",
-                    "Prepare interaction scripts: questions for audience polls or discussion, expected responses, and how you will synthesize them back into your presentation.",
-                    "Write backup slides for anticipated deep-dive questions on your most complex or contentious points."
-                ],
-                "outputRequired": {
-                    "slideContent": "Full slide content and speaker notes for every slide in the outline.",
-                    "backupSlides": "Backup slides for anticipated deep-dive questions."
-                },
-                "verify": [
-                    "Does every slide's content trace back to the core message and the audience's needs?",
-                    "Do the speaker notes sound like something you would actually say?"
-                ]
-            },
-            "askForFiles": true,
-            "requireConfirmation": false
+        "verify": [
+          "Does the outline tell a coherent story from opening to close?",
+          "Does the pacing feel right for the stated time budget?",
+          "Is there at least one engagement moment in the first third of the presentation?"
+        ]
+      },
+      "requireConfirmation": true
+    },
+    {
+      "id": "content-development",
+      "title": "Content Development",
+      "promptBlocks": {
+        "goal": "Write the actual presentation content \u2014 slide text and speaker notes \u2014 following the approved outline. Every piece of content should be grounded in your audience profile and core message.",
+        "constraints": [
+          "Write for the ear, not the eye. Slide text should be sparse; speaker notes should sound natural when spoken aloud.",
+          "Use active voice and concrete language. Replace abstractions with specific examples.",
+          "Prepare backup content for questions or extended time: 2-3 extra slides that can be shown if needed."
+        ],
+        "procedure": [
+          "For each slide in your outline, write the visible slide content: headline, key bullets or visual description, and any data or quotes.",
+          "Write speaker notes for each slide: talking points, transitions to the next slide, and timing cues.",
+          "Develop your key stories and examples in full: the narrative, the specific detail that makes it vivid, and the connection back to your core message.",
+          "Prepare interaction scripts: questions for audience polls or discussion, expected responses, and how you will synthesize them back into your presentation.",
+          "Write backup slides for anticipated deep-dive questions on your most complex or contentious points."
+        ],
+        "outputRequired": {
+          "slideContent": "Full slide content and speaker notes for every slide in the outline.",
+          "backupSlides": "Backup slides for anticipated deep-dive questions."
         },
-        {
-            "id": "delivery-preparation",
-            "title": "Delivery Preparation",
-            "promptBlocks": {
-                "goal": "Create a delivery preparation plan tailored to your specific presentation context: the format (in-person, remote, recorded), the venue, and your personal readiness.",
-                "constraints": [
-                    "Adapt this plan to the actual delivery context. Remote and in-person presentations have very different risk profiles.",
-                    "Practice advice should be actionable, not generic. 'Practice out loud three times with slides' is useful; 'be confident' is not.",
-                    "Q&A preparation matters as much as the main content for high-stakes presentations."
-                ],
-                "procedure": [
-                    "Define your practice schedule: how many run-throughs you need, at what level of realism (slides only vs. full setup), and target dates.",
-                    "Set timing benchmarks: target time for each major section with acceptable variance. Identify which sections you can expand or compress if needed.",
-                    "Prepare for technical setup: what equipment you need, what to test in advance, and what backup plans you have if something fails.",
-                    "Anticipate the top 5-10 questions you are likely to receive and draft short, confident responses for each.",
-                    "Plan your post-presentation follow-up: how will you share materials, continue conversations, and measure whether your call-to-action was effective?"
-                ],
-                "outputRequired": {
-                    "deliveryPlan": "Practice schedule, timing benchmarks, technical setup and backup plans, Q&A preparation, and follow-up plan."
-                },
-                "verify": [
-                    "Is this plan specific to your actual delivery context, or would it apply to any presentation?",
-                    "Have you accounted for the most likely failure modes given your setting?"
-                ]
-            },
-            "requireConfirmation": false
-        }
-    ]
+        "verify": [
+          "Does every slide's content trace back to the core message and the audience's needs?",
+          "Do the speaker notes sound like something you would actually say?"
+        ]
+      },
+      "askForFiles": true,
+      "requireConfirmation": false
+    },
+    {
+      "id": "delivery-preparation",
+      "title": "Delivery Preparation",
+      "promptBlocks": {
+        "goal": "Create a delivery preparation plan tailored to your specific presentation context: the format (in-person, remote, recorded), the venue, and your personal readiness.",
+        "constraints": [
+          "Adapt this plan to the actual delivery context. Remote and in-person presentations have very different risk profiles.",
+          "Practice advice should be actionable, not generic. 'Practice out loud three times with slides' is useful; 'be confident' is not.",
+          "Q&A preparation matters as much as the main content for high-stakes presentations."
+        ],
+        "procedure": [
+          "Define your practice schedule: how many run-throughs you need, at what level of realism (slides only vs. full setup), and target dates.",
+          "Set timing benchmarks: target time for each major section with acceptable variance. Identify which sections you can expand or compress if needed.",
+          "Prepare for technical setup: what equipment you need, what to test in advance, and what backup plans you have if something fails.",
+          "Anticipate the top 5-10 questions you are likely to receive and draft short, confident responses for each.",
+          "Plan your post-presentation follow-up: how will you share materials, continue conversations, and measure whether your call-to-action was effective?"
+        ],
+        "outputRequired": {
+          "deliveryPlan": "Practice schedule, timing benchmarks, technical setup and backup plans, Q&A preparation, and follow-up plan."
+        },
+        "verify": [
+          "Is this plan specific to your actual delivery context, or would it apply to any presentation?",
+          "Have you accounted for the most likely failure modes given your setting?"
+        ]
+      },
+      "requireConfirmation": false
+    }
+  ]
 }

package/workflows/production-readiness-audit.json

@@ -1,8 +1,8 @@
 {
   "id": "production-readiness-audit",
-  "name": "Production Readiness Audit (v2 • Evidence-Driven Readiness Review)",
+  "name": "Production Readiness Audit (v2 \u2022 Evidence-Driven Readiness Review)",
   "version": "0.1.0",
-  "description": "Audit a bounded codebase scope for debugging risk, runtime readiness, stale or misleading implementation surfaces, technical debt, and anything else that would keep it from being honestly production-ready.",
+  "description": "Use this to audit a codebase scope for production readiness. Checks debugging correctness, runtime operability, artifact realism, technical debt, and anything that would prevent honest production deployment.",
   "recommendedPreferences": {
     "recommendedAutonomy": "guided",
     "recommendedRiskPolicy": "conservative"
@@ -43,7 +43,10 @@
         "goal": "Build the minimum complete understanding needed to audit readiness honestly.",
         "constraints": [
           [
-            { "kind": "ref", "refId": "wr.refs.notes_first_durability" }
+            {
+              "kind": "ref",
+              "refId": "wr.refs.notes_first_durability"
+            }
           ],
           "Use tools first. Ask only for true scope or permission gaps you cannot resolve yourself.",
           "Separate in-scope code from adjacent noise before you classify rigor or risk."
@@ -67,8 +70,14 @@
       },
       "requireConfirmation": {
         "or": [
-          { "var": "scopeShape", "equals": "whole_codebase" },
-          { "var": "riskLevel", "equals": "High" }
+          {
+            "var": "scopeShape",
+            "equals": "whole_codebase"
+          },
+          {
+            "var": "riskLevel",
+            "equals": "High"
+          }
         ]
       }
     },
@@ -103,7 +112,10 @@
         "goal": "Freeze a neutral readiness fact packet and decide how much reviewer-family parallelism is warranted.",
         "constraints": [
           [
-            { "kind": "ref", "refId": "wr.refs.notes_first_durability" }
+            {
+              "kind": "ref",
+              "refId": "wr.refs.notes_first_durability"
+            }
           ],
           "The fact packet is the primary truth for downstream reviewer families.",
           "Keep `readinessHypothesis` as a hypothesis to challenge, not a frame to defend.",
@@ -131,12 +143,18 @@
       "promptFragments": [
         {
           "id": "phase-2-quick",
-          "when": { "var": "rigorMode", "equals": "QUICK" },
+          "when": {
+            "var": "rigorMode",
+            "equals": "QUICK"
+          },
           "text": "Keep the fact packet compact. QUICK should not manufacture a giant ceremony layer."
         },
         {
           "id": "phase-2-thorough",
-          "when": { "var": "rigorMode", "equals": "THOROUGH" },
+          "when": {
+            "var": "rigorMode",
+            "equals": "THOROUGH"
+          },
           "text": "For THOROUGH rigor, make the hidden-risk surfaces explicit: blind spots, fake confidence vectors, and production assumptions that would hurt if wrong."
         }
       ],
@@ -153,10 +171,16 @@
         "goal": "Run the selected reviewer families in parallel from the same readiness fact packet, then synthesize their output as evidence rather than conclusions.",
         "constraints": [
           [
-            { "kind": "ref", "refId": "wr.refs.notes_first_durability" }
+            {
+              "kind": "ref",
+              "refId": "wr.refs.notes_first_durability"
+            }
           ],
           [
-            { "kind": "ref", "refId": "wr.refs.synthesis_under_disagreement" }
+            {
+              "kind": "ref",
+              "refId": "wr.refs.synthesis_under_disagreement"
+            }
           ],
           "Each reviewer family must use `readinessFactPacket` as primary truth.",
           "Use `readinessHypothesis` only as comparison context.",
@@ -203,7 +227,10 @@
             "goal": "If contradictions, blind spots, or important coverage gaps remain, run only the smallest targeted follow-up needed.",
             "constraints": [
               [
-                { "kind": "ref", "refId": "wr.refs.parallelize_cognition_serialize_synthesis" }
+                {
+                  "kind": "ref",
+                  "refId": "wr.refs.parallelize_cognition_serialize_synthesis"
+                }
               ],
               "Prefer one compact targeted bundle over repeated broad delegation moments.",
               "Do not regather broad context unless a contradiction proves the original fact packet is insufficient.",
@@ -291,10 +318,16 @@
         "goal": "Stress-test the current readiness verdict before final handoff.",
         "constraints": [
           [
-            { "kind": "ref", "refId": "wr.refs.adversarial_challenge_rules" }
+            {
+              "kind": "ref",
+              "refId": "wr.refs.adversarial_challenge_rules"
+            }
           ],
           [
-            { "kind": "ref", "refId": "wr.refs.synthesis_under_disagreement" }
+            {
+              "kind": "ref",
+              "refId": "wr.refs.synthesis_under_disagreement"
+            }
           ],
           "Validation output is evidence to synthesize, not automatic authority."
         ],
@@ -319,8 +352,14 @@
       },
       "requireConfirmation": {
         "or": [
-          { "var": "finalConfidenceBand", "equals": "Low" },
-          { "var": "finalVerdict", "equals": "inconclusive" }
+          {
+            "var": "finalConfidenceBand",
+            "equals": "Low"
+          },
+          {
+            "var": "finalVerdict",
+            "equals": "inconclusive"
+          }
         ]
       }
     },