Menü
Draft content in your voice — emails, Slack messages, strategy docs, posts
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Basierend auf der SOC-Berufsklassifikation
Prepare for a 1:1 — pull context from goals, meeting notes, Slack, and tasks to generate talking points
Auto-generate or update description, type, topics, aliases, and graph-backed relationship fields for a file.
Build a focused plan for today based on goals, tasks, and recent activity. Reads from the weekly plan if it exists and updates it.
Check system health — metadata gaps, graph integrity, alias sync, and referential integrity.
Weekly review + compound learnings — review progress, surface blockers, distill insights into Memory
Cross-initiative alignment checker — surfaces misalignment, gaps, duplication, dependency risks, and synergy opportunities across active initiatives in the company and your groups roadmap. Complementary to /pulse (broad discovery); /align focuses on whether your initiatives are pulling in the same direction and have synergies with other company groups. Run ad-hoc or before key decisions.
| name | draft |
| description | Draft content in your voice — emails, Slack messages, strategy docs, posts |
Generate written content that sounds like you, not generic AI.
When the user invokes /draft [topic or description], run through all steps in sequence.
If the topic is ambiguous, ask:
Context/Reference/writing-styles/ for a format-specific guide — always read the matching file before drafting:
Context/Reference/writing-styles/slack.mdContext/Reference/writing-styles/strategy.mdContext/Memory/ for any additional voice notes or tone overridesContext/Knowledge/voice-guide.md or Context/Knowledge/voice-samples/ — if they exist, read and applyBased on the content type, pull relevant context:
| Content Type | Where to Look |
|---|---|
| Email / Slack message | Context/Meeting Notes/ for relationship context, Tasks/ for project status |
| Strategy doc / memo | GOALS.md, Context/Document Hub/, Context/Knowledge/ |
| Update / status | Context/Progress Updates/, active Tasks/, recent completions in Tasks/Done/ |
| Post / article | GOALS.md for positioning, Context/Memory/ for voice |
If MCP tools are available, check Slack or Confluence for recent threads related to the topic.
Apply these principles (override with user's voice guide if available):
Structure:
Tone:
Avoid:
Show the draft and ask:
"Here's a draft. Want me to adjust the tone (more casual / more formal), shorten or expand, or change the emphasis?"
If no voice guide or samples exist and the user wants to establish their voice:
Context/Knowledge/voice-samples/Context/Knowledge/voice-guide.md with: sentence style, openers, signature phrases, "never say" list, tone by context (internal/external/public)This only needs to happen once — future /draft runs will read the guide automatically.
Present the draft in a copy-pasteable block. Keep meta-commentary minimal — the user wants the content, not a description of the content.