| name | voice-interview |
| description | Set up the writing-voice profile. Say "set up my voice profile", "set up my voice", "voice interview", or "capture my voice" (or run /founder-os:voice-interview). This is how your WRITING sounds; if they mean talking to the OS out loud (speaking and listening), that is add-voice, not this. Interactive interview that captures rhythm, openings, closings, contractions, idiosyncrasies, and writes the result to `core/voice-profile.yml`. Asks for samples first because samples beat self-description, then asks shaping questions to fill the gaps. Extracts intent from messy real-world answers, never asks the user to be structured.
|
| why | Builds the voice profile that gates every writing skill - without it linkedin-post, email-drafter, proposal-writer, and client-update all produce generic output that does not sound like you. |
| enhance | Paste at least three real samples you have already written before answering shaping questions - samples are the ground truth and override the rules when they conflict, so more specific samples mean a sharper profile. |
| allowed-tools | ["Read","Write","Edit"] |
| mcp_requirements | [] |
Voice Interview
Runs on: local-writes - creates or edits files in your OS folder; needs an agent with write access.
You are running an interactive interview to capture the user's writing voice. The output is core/voice-profile.yml. The voice-profile feeds the your-voice skill, which then writes everything as the user from that point on.
Internal phase numbers in markdown H2 headers are for the maintainer; the operator sees a three-part frame (Part 1 of 3 - Samples, Part 2 of 3 - Shaping questions, Part 3 of 3 - Confirm and save) inside model utterances. Setup (Phase 1) and Final message (Phase 5) sit outside the three-part frame because they are pre-interview onboarding and post-save confirmation respectively.
Cross-skill asymmetry note: this skill has 5 phases. The sibling brand-voice-interview has 6 because it captures positioning (who-the-brand-sells-to) before voice (how-the-brand-speaks). Operator voice does not need a positioning phase because operator positioning lives in core/identity.md (captured by founder-os-setup). Do not collapse positioning into voice when editing the sibling skill.
Do not generate `core/voice-profile.yml` until you have collected at least 2 reference samples (pasted in chat OR sourced from existing session artifacts: `brain/rants/*.md`, `context/decisions.md`, `brain/log.md` recent entries, or `clients/*/communications/`) AND walked the shaping questions, including buyer-language questions and anti-example questions. Samples are the ground truth. If the user has no existing artifacts and refuses to paste samples, ask them to write 2 short pieces in the chat right now (a 2-sentence work email and a LinkedIn-style hook). Don't proceed without samples - the profile without samples is a stereotype.
Do not invent answers. If the user skips a question, leave the field as [NOT SET] and tell them they can re-run the interview later.
Phase map - load the reference when you reach the phase
Run the phases in order. When you reach a heavy phase, read its reference file for the full procedure, then execute it. Load only the phase you are in.
| Phase | What it does | Load |
|---|
| 1 | Setup - operator vs brand, then welcome (inline below) | - |
| 2 | Samples - scan for existing artifacts, paste flow (the ground truth) | references/samples-and-questions.md |
| 3 | Shaping questions - Q1 to Q12 including anti-examples | references/samples-and-questions.md |
