communicate

Name: communicate
Author: aleksander-dytko

31stars4forks

How to install communicate?

aleksander-dytko/ai-pm-workspace/communicate

$npx -y skills add aleksander-dytko/ai-pm-workspace --skill communicate

Installs into the current project.

Summary

Draft a professional communication (Slack, email, or async doc) with context from the vault

Files · 1

View on GitHub

SKILL.md

1	# Draft a Communication
2
3	You help draft a professional communication based on context from the vault. Channel-flexible: Slack, email, or an async update (doc comment, status page, ticket).
4
5	## Input
6
7	The user provides via `$ARGUMENTS`:
8	- What to communicate: the topic or message content
9	- To whom: the recipient or audience
10	- Channel (optional): "Slack", "email", "doc", "async update". If not specified, ask once.
11
12	Example: "update engineering on API scope change - Slack, #eng-platform".
13
14	## Workflow
15
16	1. Read relevant context:
17	- Recent meetings in `Meetings/` on this topic
18	- Recent decisions in `Loose Notes/Work/` related to the topic
19	- `Dashboard/Weekly P-Tasks.md` for current priorities
20	- Any other relevant notes found via search
21
22	2. Check recipient preferences:
23	- Read `Dashboard/people-profiles.md` for recipient's communication style (if listed).
24	- Note preferred channel, tone, level of detail.
25
26	3. Determine audience and tone:
27	- Engineering: technical, specific, actionable. Include links to specs, APIs, issues. Avoid high-level marketing language.
28	- Design: user-focused, visual references. Include user stories and customer context. Avoid deep technical detail.
29	- Leadership: strategic, metrics-driven, concise. Include business impact, metrics, goal alignment. Avoid implementation detail.
30	- Customers: professional, benefits-focused. Include business value and clear ROI. Avoid internal jargon and unfinished features.
31
32	4. Draft the message:
33	- Start with context (why this, now)
34	- Present 2-3 key points clearly
35	- End with clear next steps or call to action
36	- Format for the chosen channel:
37	- Slack: Slack markdown (`bold` single asterisk, `-` bullets, `:emoji_name:`)
38	- Email: subject line + professional email body
39	- Async doc / comment: plain Markdown, no emoji-heavy formatting, lead with the conclusion (inverted pyramid)
40
41	5. Include relevant links:
42	- Meeting notes (for prior discussions)
43	- GitHub issues (if accessible to the recipient)
44	- Any external links that support the message
45
46	## Output Format
47
48	Slack:
49	```
50	📧 Slack message for [Recipient / Channel]:
51
52	[Message ready to copy-paste with Slack markdown]
53	```
54
55	Email:
56	```
57	📧 Email draft for [Recipient]:
58
59	Subject: [Clear, concise subject line]
60
61	[Email body ready to copy-paste]
62	```
63
64	Async doc / comment:
65	```
66	📝 Async update for [Doc / Ticket / Channel]:
67
68	[Body - lead with conclusion, then context, then next steps]
69	```
70
71	## Example: Engineering Slack update
72
73	User: "update engineering on API scope change - Slack, #eng-platform"
74
75	Draft:
76	```
77	📧 Slack message for #eng-platform:
78
79	API scope update for next release
80
81	We're adjusting scope based on customer validation feedback:
82
83	In scope ✅:
84	- Business key search endpoint (epic: [link])
85	- Agent status visibility in dashboard
86	- Retry semantics clarification
87
88	Out of scope ⭕:
89	- Full execution timeline (moved to next cycle)
90
91	Why: Customer validation showed business key search is a migration blocker for 3 accounts. Timeline visualization requires UX work that doesn't fit this cycle.
92
93	Next steps:
94	- Epic sizing this week (engineering lead)
95	- Design review Thursday
96	- Updated roadmap in tracker: [link]
97
98	Questions? Thread below or ping me directly.
99	```
100
101	## Example: Leadership email
102
103	User: "draft leadership update on Q1 progress - email"
104
105	Draft:
106	```
107	📧 Email draft for leadership:
108
109	Subject: Q1 Platform Progress - Key Milestone Update
110
111	Hi team,
112
113	Quick update on Q1 progress:
114
115	Progress:
116	- 3 of 5 epics scoped and prioritized
117	- Customer validation sessions completed
118	- Top priority adjusted based on customer feedback
119
120	Metrics:
121	- On track for target release
122	- 2 epics in active development
123
124	Risks:
125	- Engineering capacity tight on one initiative
126	- Mitigation: deprioritized lower-impact work to next cycle
127
128	Next milestone: Design review [date], eng handoff [date].
129
130	Full details: [link]
131	```
132
133	## Notes
134
135	- Match the tone to the audience - don't send engineering-style updates to leadership.
136	- Keep Slack messages under 200 words (people skim).
137	- Email subject lines should be clear and actionable.
138	- Reference `Dashboard/people-profiles.md` for recipient-specific preferences.
139	- Slack markdown formatting: `bold` (single asterisk), `-` bullets, `:emoji_name:` format.

People who liked this also viewed

6 picks

Type

communicate

31stars4forks

View on GitHub

How to install communicate?

aleksander-dytko/ai-pm-workspace/communicate

$npx -y skills add aleksander-dytko/ai-pm-workspace --skill communicate

Installs into the current project.

Summary

Draft a professional communication (Slack, email, or async doc) with context from the vault

Files · 1

View on GitHub

SKILL.md

1	# Draft a Communication
2
3	You help draft a professional communication based on context from the vault. Channel-flexible: Slack, email, or an async update (doc comment, status page, ticket).
4
5	## Input
6
7	The user provides via `$ARGUMENTS`:
8	- What to communicate: the topic or message content
9	- To whom: the recipient or audience
10	- Channel (optional): "Slack", "email", "doc", "async update". If not specified, ask once.
11
12	Example: "update engineering on API scope change - Slack, #eng-platform".
13
14	## Workflow
15
16	1. Read relevant context:
17	- Recent meetings in `Meetings/` on this topic
18	- Recent decisions in `Loose Notes/Work/` related to the topic
19	- `Dashboard/Weekly P-Tasks.md` for current priorities
20	- Any other relevant notes found via search
21
22	2. Check recipient preferences:
23	- Read `Dashboard/people-profiles.md` for recipient's communication style (if listed).
24	- Note preferred channel, tone, level of detail.
25
26	3. Determine audience and tone:
27	- Engineering: technical, specific, actionable. Include links to specs, APIs, issues. Avoid high-level marketing language.
28	- Design: user-focused, visual references. Include user stories and customer context. Avoid deep technical detail.
29	- Leadership: strategic, metrics-driven, concise. Include business impact, metrics, goal alignment. Avoid implementation detail.
30	- Customers: professional, benefits-focused. Include business value and clear ROI. Avoid internal jargon and unfinished features.
31
32	4. Draft the message:
33	- Start with context (why this, now)
34	- Present 2-3 key points clearly
35	- End with clear next steps or call to action
36	- Format for the chosen channel:
37	- Slack: Slack markdown (`bold` single asterisk, `-` bullets, `:emoji_name:`)
38	- Email: subject line + professional email body
39	- Async doc / comment: plain Markdown, no emoji-heavy formatting, lead with the conclusion (inverted pyramid)
40
41	5. Include relevant links:
42	- Meeting notes (for prior discussions)
43	- GitHub issues (if accessible to the recipient)
44	- Any external links that support the message
45
46	## Output Format
47
48	Slack:
49	```
50	📧 Slack message for [Recipient / Channel]:
51
52	[Message ready to copy-paste with Slack markdown]
53	```
54
55	Email:
56	```
57	📧 Email draft for [Recipient]:
58
59	Subject: [Clear, concise subject line]
60
61	[Email body ready to copy-paste]
62	```
63
64	Async doc / comment:
65	```
66	📝 Async update for [Doc / Ticket / Channel]:
67
68	[Body - lead with conclusion, then context, then next steps]
69	```
70
71	## Example: Engineering Slack update
72
73	User: "update engineering on API scope change - Slack, #eng-platform"
74
75	Draft:
76	```
77	📧 Slack message for #eng-platform:
78
79	API scope update for next release
80
81	We're adjusting scope based on customer validation feedback:
82
83	In scope ✅:
84	- Business key search endpoint (epic: [link])
85	- Agent status visibility in dashboard
86	- Retry semantics clarification
87
88	Out of scope ⭕:
89	- Full execution timeline (moved to next cycle)
90
91	Why: Customer validation showed business key search is a migration blocker for 3 accounts. Timeline visualization requires UX work that doesn't fit this cycle.
92
93	Next steps:
94	- Epic sizing this week (engineering lead)
95	- Design review Thursday
96	- Updated roadmap in tracker: [link]
97
98	Questions? Thread below or ping me directly.
99	```
100
101	## Example: Leadership email
102
103	User: "draft leadership update on Q1 progress - email"
104
105	Draft:
106	```
107	📧 Email draft for leadership:
108
109	Subject: Q1 Platform Progress - Key Milestone Update
110
111	Hi team,
112
113	Quick update on Q1 progress:
114
115	Progress:
116	- 3 of 5 epics scoped and prioritized
117	- Customer validation sessions completed
118	- Top priority adjusted based on customer feedback
119
120	Metrics:
121	- On track for target release
122	- 2 epics in active development
123
124	Risks:
125	- Engineering capacity tight on one initiative
126	- Mitigation: deprioritized lower-impact work to next cycle
127
128	Next milestone: Design review [date], eng handoff [date].
129
130	Full details: [link]
131	```
132
133	## Notes
134
135	- Match the tone to the audience - don't send engineering-style updates to leadership.
136	- Keep Slack messages under 200 words (people skim).
137	- Email subject lines should be clear and actionable.
138	- Reference `Dashboard/people-profiles.md` for recipient-specific preferences.
139	- Slack markdown formatting: `bold` (single asterisk), `-` bullets, `:emoji_name:` format.

People who liked this also viewed

6 picks

Type