First-run voice calibration — deep scan, sample collection, Q&A, voice analysis. 5-10 minutes.
From draftnpx claudepluginhub tenfourty/cc-marketplace --plugin draft/setupInitializes or resumes project setup via interactive Q&A, creating conductor/ artifacts for product definition, guidelines, tech stack, workflow, and style guides.
/setupDetects ghost Claude plugin installations by checking cache, registry, and temp files on macOS/Linux/Windows; cleans up on user confirmation.
/setupChecks local Codex CLI readiness, prompts to install if unavailable via npm, and optionally toggles stop-time review gate.
/setupGuides enterprise admins through Claude Office add-in setup for Vertex AI, Bedrock, or custom gateway; provisions credentials and generates deployable manifest.xml.
/setupConfigures claude-hud as Claude Code statusline by providing ~/.claude/settings.json config, build instructions, manual setup, and troubleshooting steps.
/setupRuns interactive setup wizard: detects AI providers (Codex, Gemini, Ollama, etc.), RTK token optimizer, system tools; displays status table; offers to install/configure missing items.
Rich onboarding to calibrate the draft to your authentic voice. Scans your messaging history, collects samples, asks questions, then saves a voice profile and style examples to kbx for future sessions.
Conversational and collaborative. You're learning about the user's voice, not lecturing them. One question at a time.
Check for an existing profile:
Check if memory/draft/voice-profile.md exists (Read tool)
| Condition | Action |
|---|---|
| Profile exists | Show current profile summary, offer: update, start fresh, or cancel |
| No profile | Proceed with setup |
Let's calibrate your voice. This takes about 5-10 minutes — I'll scan your recent messages, ask some questions, and build a voice profile.
At the end, I'll save everything so future drafting sessions sound like you.
Spawn a background worker to scan the user's messaging history:
Slack scan (if Slack MCP available):
slack_search_public for recent messages from the user across channelsGmail scan (if Gmail MCP available):
gmail_search_messages for recent sent emailsWhile the scan runs, proceed to Phase 2.
Present scan findings when available:
I found [N] messages across [M] contexts. Here are the ones that seem most distinctive:
[Show 3-5 most characteristic messages with detected style labels]
Then ask:
Do you have 2-3 additional messages that feel most "you"? Paste them here or share Slack links.
These are the messages where someone who knows you would say "that's definitely [Name]."
Accept:
slack_read_thread or slack_read_channel MCPAsk these in sequence. Use AskUserQuestion with multiple-choice where possible. Skip questions that are already clearly answered by the scan data.
Q1: Role and audience
What's your role, and who do you primarily communicate with? (This helps me calibrate formality and authority level.)
Q2: Tone (3 words)
How would you describe your communication style in 3 words?
Q3: Language
Which English spelling convention do you use?
- British English (colour, organise, behaviour)
- American English (color, organize, behavior)
- Other / mixed
Q4: Greetings
How do you typically open group messages? (e.g., "Hi folks", "Hey team", "Good morning everyone")
Q5: Sign-offs
How do you close messages? (e.g., just your name, "Thanks!", "Have a great weekend!", no sign-off)
Q6: Anti-patterns
Any words or phrases you hate or want to avoid? Corporate jargon, particular expressions, anything that makes you cringe when you see it in a message?
Q7: Emoji
How do you use emoji?
- Sparingly and naturally (1-2 per message max)
- Frequently (multiple per message, emoji reactions)
- Rarely / never
Q8: Formatting
Do you prefer bullets, prose, or mixed? Do you use bold for emphasis?
Q9: Overused phrases
Any patterns you tend to overuse that we should vary? (Most people have 2-3.)
Q10: Sensitive topics
Any topics that need special care? (Sensitive projects, specific people, political subjects within the org.)
Synthesise all data (scan + samples + Q&A) into a voice fingerprint:
Analyse patterns across all collected messages:
Detect communication styles from the corpus:
Present the profile:
Here's what I've learned about your voice:
Identity: [role, tone description] Language: [spelling, greetings, sign-offs] Writing cadence: [sentence rhythm, paragraph style] Formatting: [emoji, bold, bullets preferences] Anti-patterns: [words to avoid] Sensitive topics: [areas needing care]
Detected styles (with example counts):
- Strategic Announcement: [N] examples
- Action-Oriented: [N] examples
- [etc.]
- [Custom style if detected]: [N] examples
Does this capture your voice? Anything to adjust?
Accept adjustments, then save:
Voice profile — write to memory/draft/voice-profile.md:
skills/voice-identity/SKILL.mdStyle files — write to memory/draft/styles/<style-name>.md for each detected style:
Confirm:
Voice profile saved with [N] style files.
You can update anytime by running
/draft:setupagain.Ready to draft something? Run
/draft:bootor just tell me what you need.
| Missing | Fallback |
|---|---|
| Slack MCP unavailable | Skip deep scan. Ask user to paste 5-10 sample messages instead. |
| Gmail MCP unavailable | Skip email scan. Slack + pasted samples are enough. |
| Both MCPs unavailable | Full manual mode — rely on pasted samples + Q&A only. |
| User skips questions | Work with whatever they provide — any data is better than none. |
| kbx/file write fails | Present the profile as formatted text for the user to save manually. |