Artifact generation protocol
Generate presentation-grade content: decks, narratives, speeches, thought leadership pieces, panel prep, event session content.
Step 1: Intake
Gather from user or infer:
- Topic: What is this about?
- Audience: Who will consume this? (board, industry conference, internal all-hands, specific stakeholder)
- Format: Deck / Narrative / Speech
- Key messages: What must be conveyed?
- Time constraints: Presentation length or reading time
- Event type: If applicable (conference, board meeting, team meeting)
If critical intake info is missing, apply clarification protocol.
Step 2: Context gathering
Load relevant context:
memory/initiatives/_index.md + targeted initiative filesmemory/products/_index.md + targeted product filesmemory/decisions/_index.md + relevant decisionsmemory/people/{stakeholder}.md for audience-specific adaptationcontexts/ for deep reference material- Recent
journal/ entries for freshness and recency
Step 3: Format-specific generation
Deck format
Slide-by-slide outline:
## Slide 1: [Title]
**Key points:**
- [Point 1]
- [Point 2]
**Speaker notes:**
[What to say when presenting this slide]
**Suggested visual:**
[Chart type, image concept, or data visualization]
Structure: Opening (hook + agenda) -> Body (3-5 key sections) -> Close (summary + call to action)
Narrative format
Long-form piece with:
- BLUF (opening summary)
- Supporting arguments with data points
- Stakeholder-relevant framing
- Call to action or next steps
Apply stakeholder-comms protocol for audience adaptation (UPSTREAM/DOWNSTREAM/EXTERNAL).
Speech format
Structured with:
- Opening hook (story, provocative question, or bold statement)
- Key sections with timing guidance (e.g., "~3 min")
- Transitions between sections
- Closing (callback to opening, clear ask, or memorable statement)
- Conversational tone calibrated to audience:
- Board: formal, data-driven, concise
- Industry conference: thought-leadership, forward-looking
- Internal all-hands: authentic, motivating, transparent
Step 4: Audience adaptation
| Audience type |
Adaptation |
| Upstream (Board, CEO, CPO) |
BLUF, ROI focus, concise, strategic framing |
| Downstream (Team) |
Context-rich, motivating, clear RASCI |
| External (Conference, partners) |
Thought leadership, industry framing, no internal jargon |
Step 5: Review pass
Strategic analysis light:
- Are claims supported by known data (from memory/contexts)?
- Is messaging consistent with known initiatives and decisions?
- Are there political sensitivities? (Check stakeholder profiles)
- Would the CTO or CPO object to anything? (Quick mental validation)
Output
Save to contexts/artifacts/YYYY-MM-DD-artifact-slug.md
---
date: YYYY-MM-DD
title: Artifact Title
type: deck | narrative | speech
audience: Board | Conference | Team | Stakeholder Name
topic: Primary topic
initiatives: [Related initiatives]
---
Display the artifact to the user and confirm save location.
Context budget
- Memory: Read
_index.md + up to 5 targeted files
- Contexts: Up to 3 reference documents
- Journal: Current month
_index.md + up to 2 recent entries for freshness
Absolute constraints
- NEVER generate without understanding the audience
- NEVER skip the review pass
- NEVER use banned phrases from communication skill
- ALWAYS save artifacts to
contexts/artifacts/
- ALWAYS apply audience-appropriate tone and framing
1---2name: create-33description: Generate presentation-grade decks, narratives, and speeches with audience adaptation4---5
6# Artifact generation protocol
7
8Generate presentation-grade content: decks, narratives, speeches, thought leadership pieces, panel prep, event session content.
9
10---
11
12## Step 1: Intake
13
14Gather from user or infer:
15- **Topic**: What is this about?
16- **Audience**: Who will consume this? (board, industry conference, internal all-hands, specific stakeholder)
17- **Format**: Deck / Narrative / Speech
18- **Key messages**: What must be conveyed?
19- **Time constraints**: Presentation length or reading time
20- **Event type**: If applicable (conference, board meeting, team meeting)
21
22If critical intake info is missing, apply clarification protocol.
23
24---
25
26## Step 2: Context gathering
27
28Load relevant context:
29- `memory/initiatives/_index.md` + targeted initiative files
30- `memory/products/_index.md` + targeted product files
31- `memory/decisions/_index.md` + relevant decisions
32- `memory/people/{stakeholder}.md` for audience-specific adaptation
33- `contexts/` for deep reference material
34- Recent `journal/` entries for freshness and recency
35
36---
37
38## Step 3: Format-specific generation
39
40### Deck format
41
42Slide-by-slide outline:
43```markdown
44## Slide 1: [Title]
45**Key points:**
46- [Point 1]
47- [Point 2]
48
49**Speaker notes:**
50[What to say when presenting this slide]
51
52**Suggested visual:**
53[Chart type, image concept, or data visualization]
54```
55
56Structure: Opening (hook + agenda) -> Body (3-5 key sections) -> Close (summary + call to action)
57
58### Narrative format
59
60Long-form piece with:
61- BLUF (opening summary)
62- Supporting arguments with data points
63- Stakeholder-relevant framing
64- Call to action or next steps
65
66Apply stakeholder-comms protocol for audience adaptation (UPSTREAM/DOWNSTREAM/EXTERNAL).
67
68### Speech format
69
70Structured with:
71- Opening hook (story, provocative question, or bold statement)
72- Key sections with timing guidance (e.g., "~3 min")
73- Transitions between sections
74- Closing (callback to opening, clear ask, or memorable statement)
75- Conversational tone calibrated to audience:
76 - Board: formal, data-driven, concise
77 - Industry conference: thought-leadership, forward-looking
78 - Internal all-hands: authentic, motivating, transparent
79
80---
81
82## Step 4: Audience adaptation
83
84| Audience type | Adaptation |
85|---------------|------------|
86| **Upstream** (Board, CEO, CPO) | BLUF, ROI focus, concise, strategic framing |
87| **Downstream** (Team) | Context-rich, motivating, clear RASCI |
88| **External** (Conference, partners) | Thought leadership, industry framing, no internal jargon |
89
90---
91
92## Step 5: Review pass
93
94Strategic analysis light:
95- Are claims supported by known data (from memory/contexts)?
96- Is messaging consistent with known initiatives and decisions?
97- Are there political sensitivities? (Check stakeholder profiles)
98- Would the CTO or CPO object to anything? (Quick mental validation)
99
100---
101
102## Output
103
104Save to `contexts/artifacts/YYYY-MM-DD-artifact-slug.md`
105
106```yaml
107---
108date: YYYY-MM-DD
109title: Artifact Title
110type: deck | narrative | speech
111audience: Board | Conference | Team | Stakeholder Name
112topic: Primary topic
113initiatives: [Related initiatives]
114---
115```
116
117Display the artifact to the user and confirm save location.
118
119---
120
121## Context budget
122- Memory: Read `_index.md` + up to 5 targeted files
123- Contexts: Up to 3 reference documents
124- Journal: Current month `_index.md` + up to 2 recent entries for freshness
125
126---
127
128## Absolute constraints
129
130- NEVER generate without understanding the audience
131- NEVER skip the review pass
132- NEVER use banned phrases from communication skill
133- ALWAYS save artifacts to `contexts/artifacts/`
134- ALWAYS apply audience-appropriate tone and framing
majiayu000