@exaudeus/workrail 3.12.0 → 3.13.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/dist/console/assets/{index-CRgjJiMS.js → index-EsSXrC_a.js} +11 -11
- package/dist/console/index.html +1 -1
- package/dist/di/container.js +8 -0
- package/dist/di/tokens.d.ts +1 -0
- package/dist/di/tokens.js +1 -0
- package/dist/infrastructure/session/HttpServer.js +2 -14
- package/dist/manifest.json +83 -43
- package/dist/mcp/boundary-coercion.d.ts +2 -0
- package/dist/mcp/boundary-coercion.js +73 -0
- package/dist/mcp/handler-factory.d.ts +1 -1
- package/dist/mcp/handler-factory.js +13 -6
- package/dist/mcp/handlers/v2-manage-workflow-source.d.ts +7 -0
- package/dist/mcp/handlers/v2-manage-workflow-source.js +50 -0
- package/dist/mcp/server.js +2 -0
- package/dist/mcp/tool-descriptions.js +20 -0
- package/dist/mcp/tools.js +6 -0
- package/dist/mcp/types/tool-description-types.d.ts +1 -1
- package/dist/mcp/types/tool-description-types.js +1 -0
- package/dist/mcp/types/workflow-tool-edition.d.ts +1 -1
- package/dist/mcp/types.d.ts +2 -0
- package/dist/mcp/v2/tool-registry.js +8 -0
- package/dist/mcp/v2/tools.d.ts +12 -0
- package/dist/mcp/v2/tools.js +7 -1
- package/dist/v2/infra/in-memory/managed-source-store/index.d.ts +8 -0
- package/dist/v2/infra/in-memory/managed-source-store/index.js +33 -0
- package/dist/v2/infra/local/data-dir/index.d.ts +2 -0
- package/dist/v2/infra/local/data-dir/index.js +6 -0
- package/dist/v2/infra/local/managed-source-store/index.d.ts +15 -0
- package/dist/v2/infra/local/managed-source-store/index.js +164 -0
- package/dist/v2/ports/data-dir.port.d.ts +2 -0
- package/dist/v2/ports/managed-source-store.port.d.ts +25 -0
- package/dist/v2/ports/managed-source-store.port.js +2 -0
- package/package.json +1 -1
- package/workflows/adaptive-ticket-creation.json +276 -282
- package/workflows/document-creation-workflow.json +70 -191
- package/workflows/documentation-update-workflow.json +59 -309
- package/workflows/intelligent-test-case-generation.json +37 -212
- package/workflows/personal-learning-materials-creation-branched.json +1 -21
- package/workflows/presentation-creation.json +143 -308
- package/workflows/relocation-workflow-us.json +161 -535
- package/workflows/scoped-documentation-workflow.json +110 -181
- package/workflows/workflow-for-workflows.v2.json +21 -5
- package/workflows/CHANGELOG-bug-investigation.md +0 -298
- package/workflows/bug-investigation.agentic.json +0 -212
- package/workflows/bug-investigation.json +0 -112
- package/workflows/mr-review-workflow.agentic.json +0 -538
- package/workflows/mr-review-workflow.json +0 -277
|
@@ -1,330 +1,165 @@
|
|
|
1
1
|
{
|
|
2
2
|
"id": "presentation-creation",
|
|
3
|
-
"name": "
|
|
4
|
-
"version": "
|
|
5
|
-
"description": "
|
|
3
|
+
"name": "Presentation Creation Workflow",
|
|
4
|
+
"version": "1.0.0",
|
|
5
|
+
"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.",
|
|
6
6
|
"preconditions": [
|
|
7
|
-
"
|
|
8
|
-
"
|
|
9
|
-
"
|
|
10
|
-
"User has a rough timeline for presentation delivery"
|
|
7
|
+
"You have a clear presentation topic or objective.",
|
|
8
|
+
"You know roughly who your audience is.",
|
|
9
|
+
"You have access to any source materials or data you plan to reference."
|
|
11
10
|
],
|
|
12
11
|
"clarificationPrompts": [
|
|
13
12
|
"What is the main objective or key message of your presentation?",
|
|
14
|
-
"Who is your target audience and what is their
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
"
|
|
18
|
-
"
|
|
13
|
+
"Who is your target audience and what is their professional context?"
|
|
14
|
+
],
|
|
15
|
+
"metaGuidance": [
|
|
16
|
+
"Ground every decision in your audience profile. Generic presentations fail because they are not written for anyone specific.",
|
|
17
|
+
"Each step should explicitly reference outputs from the previous step to avoid boilerplate drift.",
|
|
18
|
+
"Prioritize clarity over completeness. A tight presentation that lands one message beats a comprehensive one that loses the audience.",
|
|
19
|
+
"Build in engagement moments throughout, not just at the opening.",
|
|
20
|
+
"Every section should pass the 'so what?' test: if the audience cannot articulate why they should care, cut or reframe.",
|
|
21
|
+
"Always have a clear call-to-action. Tell the audience what you want them to do or believe after your presentation.",
|
|
22
|
+
"Test all technical elements well before your presentation day.",
|
|
23
|
+
"Prepare contingency plans for common problems: technology failures, timing overruns, tough questions."
|
|
19
24
|
],
|
|
20
25
|
"steps": [
|
|
21
26
|
{
|
|
22
27
|
"id": "audience-and-context-analysis",
|
|
23
28
|
"title": "Audience & Context Analysis",
|
|
24
|
-
"
|
|
25
|
-
|
|
26
|
-
|
|
27
|
-
|
|
28
|
-
|
|
29
|
-
|
|
30
|
-
|
|
31
|
-
|
|
32
|
-
|
|
33
|
-
|
|
34
|
-
"
|
|
35
|
-
"
|
|
36
|
-
"
|
|
37
|
-
|
|
38
|
-
{
|
|
39
|
-
"
|
|
40
|
-
|
|
41
|
-
|
|
42
|
-
|
|
43
|
-
|
|
44
|
-
|
|
45
|
-
|
|
46
|
-
|
|
47
|
-
}
|
|
48
|
-
],
|
|
49
|
-
"hasValidation": true
|
|
50
|
-
},
|
|
51
|
-
{
|
|
52
|
-
"id": "content-strategy-and-structure",
|
|
53
|
-
"title": "Content Strategy & Structure Development",
|
|
54
|
-
"prompt": "**PREP**: Develop a compelling content strategy that aligns with your audience analysis.\n\n**IMPLEMENT**: Create a structured content plan:\n- **Core Message**: One clear, memorable takeaway (elevator pitch version)\n- **Supporting Arguments**: 3-5 key points that reinforce your core message\n- **Narrative Arc**: How will you take the audience on a journey? (problem \u2192 solution \u2192 impact)\n- **Evidence Strategy**: Data, examples, stories, and visuals that support each point\n- **Engagement Hooks**: Surprising statistics, thought-provoking questions, interactive elements\n- **Call-to-Action**: What specific action do you want the audience to take?\n\n**VERIFY**: Ensure your content strategy creates a logical flow that serves your audience's needs while achieving your objectives.",
|
|
55
|
-
"agentRole": "You are a presentation design expert and storytelling specialist with extensive experience in crafting compelling content strategies. Your expertise lies in transforming complex information into engaging narratives that drive audience action and understanding.",
|
|
56
|
-
"guidance": [
|
|
57
|
-
"Start with your core message - everything else should support it",
|
|
58
|
-
"Use the 'So What?' test for each section - why should the audience care?",
|
|
59
|
-
"Plan for multiple learning styles - visual, auditory, kinesthetic",
|
|
60
|
-
"Include moments of high engagement throughout, not just at the beginning"
|
|
61
|
-
],
|
|
62
|
-
"requireConfirmation": true,
|
|
63
|
-
"validationCriteria": [
|
|
64
|
-
{
|
|
65
|
-
"type": "regex",
|
|
66
|
-
"pattern": "(?i)##?\\s*Core Message:?",
|
|
67
|
-
"message": "Strategy must include a clear core message"
|
|
68
|
-
},
|
|
69
|
-
{
|
|
70
|
-
"type": "regex",
|
|
71
|
-
"pattern": "(?i)##?\\s*Supporting Arguments:?",
|
|
72
|
-
"message": "Strategy must include supporting arguments"
|
|
73
|
-
},
|
|
74
|
-
{
|
|
75
|
-
"type": "regex",
|
|
76
|
-
"pattern": "(?i)##?\\s*Call-to-Action:?",
|
|
77
|
-
"message": "Strategy must include a call-to-action"
|
|
78
|
-
},
|
|
79
|
-
{
|
|
80
|
-
"type": "length",
|
|
81
|
-
"min": 600,
|
|
82
|
-
"message": "Strategy should be at least 600 characters for comprehensive planning"
|
|
83
|
-
}
|
|
84
|
-
],
|
|
85
|
-
"hasValidation": true
|
|
86
|
-
},
|
|
87
|
-
{
|
|
88
|
-
"id": "slide-structure-and-flow",
|
|
89
|
-
"title": "Slide Structure & Flow Design",
|
|
90
|
-
"prompt": "**PREP**: Transform your content strategy into a detailed slide-by-slide structure.\n\n**IMPLEMENT**: Create a comprehensive slide outline:\n- **Opening Hook** (1-2 slides): Attention grabber, context setting, agenda preview\n- **Main Content Blocks** (8-15 slides): Each supporting argument with evidence and examples\n- **Transition Slides**: Smooth connections between major sections\n- **Interaction Points**: Polls, Q&A moments, discussion breaks\n- **Visual Hierarchy**: Which slides need charts, images, diagrams, or minimal text\n- **Pacing Strategy**: Balance of information density vs. breathing room\n- **Closing Impact** (2-3 slides): Summary, call-to-action, next steps\n\n**VERIFY**: Review the flow for logical progression, appropriate pacing, and engagement variety.",
|
|
91
|
-
"agentRole": "You are a presentation structure architect with expertise in information design and audience engagement flow. Your specialty is creating logical, well-paced slide sequences that maintain audience attention while effectively conveying complex information.",
|
|
92
|
-
"guidance": [
|
|
93
|
-
"Follow the 6x6 rule: max 6 bullet points with 6 words each",
|
|
94
|
-
"Plan for one key idea per slide",
|
|
95
|
-
"Include slide numbers and estimated timing",
|
|
96
|
-
"Consider how slides will work both in-person and if shared later"
|
|
97
|
-
],
|
|
98
|
-
"requireConfirmation": true,
|
|
99
|
-
"validationCriteria": [
|
|
100
|
-
{
|
|
101
|
-
"type": "regex",
|
|
102
|
-
"pattern": "(?i)slide\\s*\\d+",
|
|
103
|
-
"message": "Outline must include numbered slides (e.g., 'Slide 1', 'Slide 2')"
|
|
104
|
-
},
|
|
105
|
-
{
|
|
106
|
-
"type": "regex",
|
|
107
|
-
"pattern": "(?i)(opening|hook|introduction)",
|
|
108
|
-
"message": "Outline must include opening/hook slides"
|
|
109
|
-
},
|
|
110
|
-
{
|
|
111
|
-
"type": "regex",
|
|
112
|
-
"pattern": "(?i)(closing|conclusion|summary)",
|
|
113
|
-
"message": "Outline must include closing/summary slides"
|
|
114
|
-
},
|
|
115
|
-
{
|
|
116
|
-
"type": "length",
|
|
117
|
-
"min": 800,
|
|
118
|
-
"message": "Slide outline should be at least 800 characters for detailed planning"
|
|
119
|
-
}
|
|
120
|
-
],
|
|
121
|
-
"hasValidation": true
|
|
122
|
-
},
|
|
123
|
-
{
|
|
124
|
-
"id": "visual-design-and-engagement",
|
|
125
|
-
"title": "Visual Design & Engagement Elements",
|
|
126
|
-
"prompt": "**PREP**: Design the visual and interactive elements that will make your presentation dynamic and memorable.\n\n**IMPLEMENT**: Plan comprehensive visual and engagement strategy:\n- **Visual Theme**: Color scheme, typography, consistent design language\n- **Data Visualization**: Chart types, infographic concepts, before/after comparisons\n- **Multimedia Elements**: Video clips, animations, interactive demos\n- **Storytelling Visuals**: Metaphors, analogies, journey maps\n- **Engagement Techniques**: Live polls, breakout discussions, hands-on activities\n- **Memory Aids**: Mnemonics, repeated visual themes, callback references\n- **Accessibility**: Readable fonts, color contrast, alternative text descriptions\n\n**VERIFY**: Ensure visual elements enhance rather than distract from your message, and engagement techniques fit naturally into your flow.",
|
|
127
|
-
"agentRole": "You are a UX/visual design consultant and engagement specialist with expertise in presentation design and audience interaction. Your strength lies in creating cohesive visual experiences that enhance message delivery while maintaining accessibility and professional standards.",
|
|
128
|
-
"guidance": [
|
|
129
|
-
"Visuals should simplify complex ideas, not complicate simple ones",
|
|
130
|
-
"Use consistent visual language throughout the presentation",
|
|
131
|
-
"Plan interactive elements that serve your learning objectives",
|
|
132
|
-
"Consider how visual elements will reproduce in different formats (print, mobile, etc.)"
|
|
133
|
-
],
|
|
134
|
-
"requireConfirmation": true,
|
|
135
|
-
"validationCriteria": [
|
|
136
|
-
{
|
|
137
|
-
"type": "regex",
|
|
138
|
-
"pattern": "(?i)##?\\s*Visual Theme:?",
|
|
139
|
-
"message": "Design plan must include visual theme section"
|
|
140
|
-
},
|
|
141
|
-
{
|
|
142
|
-
"type": "regex",
|
|
143
|
-
"pattern": "(?i)##?\\s*Engagement Techniques:?",
|
|
144
|
-
"message": "Design plan must include engagement techniques"
|
|
145
|
-
},
|
|
146
|
-
{
|
|
147
|
-
"type": "length",
|
|
148
|
-
"min": 500,
|
|
149
|
-
"message": "Visual design plan should be at least 500 characters for comprehensive coverage"
|
|
150
|
-
}
|
|
151
|
-
],
|
|
152
|
-
"hasValidation": true
|
|
29
|
+
"promptBlocks": {
|
|
30
|
+
"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.",
|
|
31
|
+
"constraints": [
|
|
32
|
+
"Be specific, not categorical. 'Senior engineers at a fintech startup' is useful; 'technical professionals' is not.",
|
|
33
|
+
"Address both explicit needs (what they asked for) and implicit needs (what they actually need to hear).",
|
|
34
|
+
"Consider the broader context: what happens before and after your presentation? What mood will the audience be in?"
|
|
35
|
+
],
|
|
36
|
+
"procedure": [
|
|
37
|
+
"Define the audience: professional background, expertise level, role and seniority mix, and any relevant cultural or organizational context.",
|
|
38
|
+
"Identify audience motivations: what do they want to learn or decide? What pain points or pressures are they carrying into the room?",
|
|
39
|
+
"Analyze the presentation context: event type (conference, internal meeting, client pitch, webinar), setting (in-person, remote, hybrid), time constraints, and follow-up expectations.",
|
|
40
|
+
"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?",
|
|
41
|
+
"Identify risks: what might cause the audience to disengage, push back, or leave confused?"
|
|
42
|
+
],
|
|
43
|
+
"outputRequired": {
|
|
44
|
+
"audienceProfile": "A concise profile covering: demographics and expertise, motivations and pain points, context and setting, success definition, and key engagement risks."
|
|
45
|
+
},
|
|
46
|
+
"verify": [
|
|
47
|
+
"Does every section contain specific, actionable detail rather than generic categories?",
|
|
48
|
+
"Could you use this profile to make a real content decision right now?"
|
|
49
|
+
]
|
|
50
|
+
},
|
|
51
|
+
"requireConfirmation": true
|
|
153
52
|
},
|
|
154
53
|
{
|
|
155
|
-
"id": "content-
|
|
156
|
-
"title": "Content
|
|
157
|
-
"
|
|
158
|
-
|
|
159
|
-
|
|
160
|
-
|
|
161
|
-
|
|
162
|
-
|
|
163
|
-
|
|
164
|
-
|
|
165
|
-
|
|
166
|
-
|
|
167
|
-
|
|
168
|
-
|
|
169
|
-
"
|
|
170
|
-
|
|
171
|
-
|
|
172
|
-
|
|
173
|
-
|
|
174
|
-
|
|
175
|
-
"
|
|
176
|
-
"
|
|
177
|
-
|
|
178
|
-
|
|
179
|
-
|
|
180
|
-
"min": 1000,
|
|
181
|
-
"message": "Content development should be at least 1000 characters for comprehensive coverage"
|
|
182
|
-
}
|
|
183
|
-
],
|
|
184
|
-
"hasValidation": true
|
|
54
|
+
"id": "content-strategy",
|
|
55
|
+
"title": "Content Strategy",
|
|
56
|
+
"promptBlocks": {
|
|
57
|
+
"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.",
|
|
58
|
+
"constraints": [
|
|
59
|
+
"Start with one core message — a single, memorable sentence. Everything else should support it.",
|
|
60
|
+
"Supporting arguments should directly address the audience motivations and pain points you identified.",
|
|
61
|
+
"The narrative arc should feel natural for this audience in this context — not a generic template unless it actually fits."
|
|
62
|
+
],
|
|
63
|
+
"procedure": [
|
|
64
|
+
"State your core message: one clear, memorable sentence that captures the single most important thing you want the audience to take away.",
|
|
65
|
+
"Define 3-5 supporting arguments that reinforce your core message. For each, identify the key evidence, example, or story you will use.",
|
|
66
|
+
"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.",
|
|
67
|
+
"Plan your engagement hooks: surprising statistics, thought-provoking questions, or moments of genuine interaction that break up information delivery.",
|
|
68
|
+
"Define your call-to-action: what specific thing do you want the audience to do, believe, or decide after your presentation?"
|
|
69
|
+
],
|
|
70
|
+
"outputRequired": {
|
|
71
|
+
"contentStrategy": "Core message (one sentence), supporting arguments with evidence, narrative arc description, engagement hooks, and call-to-action."
|
|
72
|
+
},
|
|
73
|
+
"verify": [
|
|
74
|
+
"Does every supporting argument trace back to a specific audience need from your audience profile?",
|
|
75
|
+
"Does the narrative arc feel designed for this audience, or does it feel like a template?"
|
|
76
|
+
]
|
|
77
|
+
},
|
|
78
|
+
"requireConfirmation": false
|
|
185
79
|
},
|
|
186
80
|
{
|
|
187
|
-
"id": "
|
|
188
|
-
"title": "
|
|
189
|
-
"
|
|
190
|
-
|
|
191
|
-
|
|
192
|
-
|
|
193
|
-
|
|
194
|
-
|
|
195
|
-
|
|
196
|
-
"
|
|
197
|
-
|
|
198
|
-
|
|
199
|
-
|
|
200
|
-
|
|
201
|
-
|
|
202
|
-
|
|
203
|
-
|
|
204
|
-
"
|
|
205
|
-
},
|
|
206
|
-
|
|
207
|
-
"
|
|
208
|
-
"
|
|
209
|
-
"
|
|
210
|
-
|
|
211
|
-
|
|
212
|
-
|
|
213
|
-
"min": 1000,
|
|
214
|
-
"message": "Generated Markdown should be at least 1000 characters for a comprehensive presentation"
|
|
215
|
-
}
|
|
216
|
-
],
|
|
217
|
-
"hasValidation": true
|
|
81
|
+
"id": "slide-structure",
|
|
82
|
+
"title": "Slide Structure & Flow",
|
|
83
|
+
"promptBlocks": {
|
|
84
|
+
"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.",
|
|
85
|
+
"constraints": [
|
|
86
|
+
"One key idea per slide. If a slide is trying to say two things, split it.",
|
|
87
|
+
"Plan for pacing: balance information-dense slides with breathing room and interaction moments.",
|
|
88
|
+
"Think about how the slides will work if someone reads them later without you — titles should be informative, not just labels."
|
|
89
|
+
],
|
|
90
|
+
"procedure": [
|
|
91
|
+
"Opening (1-3 slides): attention-grabbing hook, context framing, and agenda or roadmap.",
|
|
92
|
+
"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.",
|
|
93
|
+
"Transitions between major sections: a single bridging slide that signals the shift and re-grounds the audience.",
|
|
94
|
+
"Closing (2-3 slides): synthesis of core message, call-to-action, next steps or contact information.",
|
|
95
|
+
"For each slide, add an estimated time in minutes and mark which slides need significant visual design work."
|
|
96
|
+
],
|
|
97
|
+
"outputRequired": {
|
|
98
|
+
"slideOutline": "A numbered slide outline. Each entry: slide number, title, content type, estimated time, and any special notes."
|
|
99
|
+
},
|
|
100
|
+
"verify": [
|
|
101
|
+
"Does the outline tell a coherent story from opening to close?",
|
|
102
|
+
"Does the pacing feel right for the stated time budget?",
|
|
103
|
+
"Is there at least one engagement moment in the first third of the presentation?"
|
|
104
|
+
]
|
|
105
|
+
},
|
|
106
|
+
"requireConfirmation": true
|
|
218
107
|
},
|
|
219
108
|
{
|
|
220
|
-
"id": "
|
|
221
|
-
"title": "
|
|
222
|
-
"
|
|
223
|
-
|
|
224
|
-
|
|
225
|
-
|
|
226
|
-
|
|
227
|
-
|
|
228
|
-
|
|
229
|
-
"
|
|
230
|
-
|
|
231
|
-
|
|
232
|
-
|
|
233
|
-
|
|
234
|
-
|
|
235
|
-
|
|
236
|
-
|
|
109
|
+
"id": "content-development",
|
|
110
|
+
"title": "Content Development",
|
|
111
|
+
"promptBlocks": {
|
|
112
|
+
"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.",
|
|
113
|
+
"constraints": [
|
|
114
|
+
"Write for the ear, not the eye. Slide text should be sparse; speaker notes should sound natural when spoken aloud.",
|
|
115
|
+
"Use active voice and concrete language. Replace abstractions with specific examples.",
|
|
116
|
+
"Prepare backup content for questions or extended time: 2-3 extra slides that can be shown if needed."
|
|
117
|
+
],
|
|
118
|
+
"procedure": [
|
|
119
|
+
"For each slide in your outline, write the visible slide content: headline, key bullets or visual description, and any data or quotes.",
|
|
120
|
+
"Write speaker notes for each slide: talking points, transitions to the next slide, and timing cues.",
|
|
121
|
+
"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.",
|
|
122
|
+
"Prepare interaction scripts: questions for audience polls or discussion, expected responses, and how you will synthesize them back into your presentation.",
|
|
123
|
+
"Write backup slides for anticipated deep-dive questions on your most complex or contentious points."
|
|
124
|
+
],
|
|
125
|
+
"outputRequired": {
|
|
126
|
+
"slideContent": "Full slide content and speaker notes for every slide in the outline.",
|
|
127
|
+
"backupSlides": "Backup slides for anticipated deep-dive questions."
|
|
128
|
+
},
|
|
129
|
+
"verify": [
|
|
130
|
+
"Does every slide's content trace back to the core message and the audience's needs?",
|
|
131
|
+
"Do the speaker notes sound like something you would actually say?"
|
|
132
|
+
]
|
|
133
|
+
},
|
|
237
134
|
"askForFiles": true,
|
|
238
|
-
"
|
|
239
|
-
{
|
|
240
|
-
"type": "regex",
|
|
241
|
-
"pattern": "(?i)(html|pdf|pptx)",
|
|
242
|
-
"message": "Output must specify and confirm one of the supported formats: HTML, PDF, or PPTX"
|
|
243
|
-
},
|
|
244
|
-
{
|
|
245
|
-
"type": "regex",
|
|
246
|
-
"pattern": "(?i)(generated.*file|marp|pandoc)",
|
|
247
|
-
"message": "Response must reference the generated presentation file and the tool used"
|
|
248
|
-
},
|
|
249
|
-
{
|
|
250
|
-
"type": "length",
|
|
251
|
-
"min": 400,
|
|
252
|
-
"message": "Generation summary and instructions should be at least 400 characters for comprehensive tool guidance"
|
|
253
|
-
}
|
|
254
|
-
],
|
|
255
|
-
"hasValidation": true
|
|
135
|
+
"requireConfirmation": false
|
|
256
136
|
},
|
|
257
137
|
{
|
|
258
|
-
"id": "
|
|
259
|
-
"title": "
|
|
260
|
-
"
|
|
261
|
-
|
|
262
|
-
|
|
263
|
-
|
|
264
|
-
|
|
265
|
-
|
|
266
|
-
|
|
267
|
-
|
|
268
|
-
|
|
269
|
-
|
|
270
|
-
|
|
271
|
-
"
|
|
272
|
-
"
|
|
273
|
-
|
|
274
|
-
|
|
275
|
-
|
|
276
|
-
|
|
277
|
-
|
|
278
|
-
"
|
|
279
|
-
|
|
280
|
-
|
|
281
|
-
|
|
282
|
-
|
|
283
|
-
"message": "Practice plan should be at least 400 characters for comprehensive preparation"
|
|
284
|
-
}
|
|
285
|
-
],
|
|
286
|
-
"hasValidation": true
|
|
287
|
-
},
|
|
288
|
-
{
|
|
289
|
-
"id": "delivery-preparation-and-logistics",
|
|
290
|
-
"title": "Delivery Preparation & Logistics",
|
|
291
|
-
"prompt": "**PREP**: Finalize all logistical and technical aspects for smooth presentation delivery.\n\n**IMPLEMENT**: Complete pre-delivery checklist:\n- **Technical Setup**: Test all equipment, backup plans, file compatibility\n- **Materials Preparation**: Printed notes, handouts, business cards, feedback forms\n- **Venue Familiarization**: Room layout, microphone, lighting, seating arrangement\n- **Personal Preparation**: Wardrobe, arrival time, pre-presentation routine\n- **Follow-up Planning**: How to share slides, continue conversations, measure impact\n- **Emergency Protocols**: Contact information, backup equipment, alternative delivery methods\n- **Final Review**: Last-minute content updates, current examples, pronunciation check\n\n**VERIFY**: Confirm all logistical elements are in place and you have contingency plans for potential issues.",
|
|
292
|
-
"agentRole": "You are an event logistics coordinator and presentation delivery specialist with expertise in ensuring flawless presentation execution. Your focus is on comprehensive preparation that anticipates and mitigates potential issues while ensuring professional delivery standards.",
|
|
293
|
-
"guidance": [
|
|
294
|
-
"Arrive early to test technology and get comfortable with the space",
|
|
295
|
-
"Have multiple backup options for critical technical components",
|
|
296
|
-
"Prepare a 'presentation day' checklist",
|
|
297
|
-
"Plan how you'll handle unexpected questions or technical difficulties"
|
|
298
|
-
],
|
|
299
|
-
"requireConfirmation": true,
|
|
300
|
-
"validationCriteria": [
|
|
301
|
-
{
|
|
302
|
-
"type": "regex",
|
|
303
|
-
"pattern": "(?i)##?\\s*Technical Setup:?",
|
|
304
|
-
"message": "Preparation must include technical setup section"
|
|
305
|
-
},
|
|
306
|
-
{
|
|
307
|
-
"type": "regex",
|
|
308
|
-
"pattern": "(?i)##?\\s*Follow-up Planning:?",
|
|
309
|
-
"message": "Preparation must include follow-up planning"
|
|
310
|
-
},
|
|
311
|
-
{
|
|
312
|
-
"type": "length",
|
|
313
|
-
"min": 300,
|
|
314
|
-
"message": "Delivery preparation should be at least 300 characters for comprehensive planning"
|
|
315
|
-
}
|
|
316
|
-
],
|
|
317
|
-
"hasValidation": true
|
|
138
|
+
"id": "delivery-preparation",
|
|
139
|
+
"title": "Delivery Preparation",
|
|
140
|
+
"promptBlocks": {
|
|
141
|
+
"goal": "Create a delivery preparation plan tailored to your specific presentation context: the format (in-person, remote, recorded), the venue, and your personal readiness.",
|
|
142
|
+
"constraints": [
|
|
143
|
+
"Adapt this plan to the actual delivery context. Remote and in-person presentations have very different risk profiles.",
|
|
144
|
+
"Practice advice should be actionable, not generic. 'Practice out loud three times with slides' is useful; 'be confident' is not.",
|
|
145
|
+
"Q&A preparation matters as much as the main content for high-stakes presentations."
|
|
146
|
+
],
|
|
147
|
+
"procedure": [
|
|
148
|
+
"Define your practice schedule: how many run-throughs you need, at what level of realism (slides only vs. full setup), and target dates.",
|
|
149
|
+
"Set timing benchmarks: target time for each major section with acceptable variance. Identify which sections you can expand or compress if needed.",
|
|
150
|
+
"Prepare for technical setup: what equipment you need, what to test in advance, and what backup plans you have if something fails.",
|
|
151
|
+
"Anticipate the top 5-10 questions you are likely to receive and draft short, confident responses for each.",
|
|
152
|
+
"Plan your post-presentation follow-up: how will you share materials, continue conversations, and measure whether your call-to-action was effective?"
|
|
153
|
+
],
|
|
154
|
+
"outputRequired": {
|
|
155
|
+
"deliveryPlan": "Practice schedule, timing benchmarks, technical setup and backup plans, Q&A preparation, and follow-up plan."
|
|
156
|
+
},
|
|
157
|
+
"verify": [
|
|
158
|
+
"Is this plan specific to your actual delivery context, or would it apply to any presentation?",
|
|
159
|
+
"Have you accounted for the most likely failure modes given your setting?"
|
|
160
|
+
]
|
|
161
|
+
},
|
|
162
|
+
"requireConfirmation": false
|
|
318
163
|
}
|
|
319
|
-
],
|
|
320
|
-
"metaGuidance": [
|
|
321
|
-
"Focus on your audience's needs and interests throughout the entire process",
|
|
322
|
-
"Prioritize clarity over complexity - your audience should easily follow your logic",
|
|
323
|
-
"Build in engagement opportunities to maintain attention and encourage participation",
|
|
324
|
-
"Practice storytelling techniques to make your content memorable and relatable",
|
|
325
|
-
"Plan for different learning styles and attention spans in your audience",
|
|
326
|
-
"Always have a clear call-to-action that tells your audience what to do next",
|
|
327
|
-
"Test all technical elements well before your presentation",
|
|
328
|
-
"Prepare for the unexpected - have backup plans for common presentation challenges"
|
|
329
164
|
]
|
|
330
|
-
}
|
|
165
|
+
}
|