writing-interviewlisted

# Writing Interview One job: collect the material only Shane has, before anything gets drafted. ## Why this exists `Profiles/voice.md`'s `do_not_infer` closes on the rule that makes this skill necessary: *"Don't generate Shane-voiced content without grounding in my actual thoughts or notes. The voice is portable. The thinking isn't."* A model can reproduce his cadence from the profile. It cannot reproduce what he saw, measured, decided, or changed his mind about. When a piece needs that material and nobody supplied it, the draft invents something that reads like it. So the interview happens first, and drafting waits. ## The hard gate **Do not draft before Shane answers.** Not an opening paragraph, not an outline presented as settled, not "here's a rough angle to react to." Ask, then wait. If the request genuinely needs no personal material — a doc rewrite, a definition, a status note — this is the wrong skill. Say so and hand off rather than running a ceremony. ## What to ask Open with one prompt, not a questionnaire. Ask for a single untidied take: > Talk to me for three to five minutes. Don't organise it. What happened that made you want to write this, who is it for, what do you believe about it, and what examples or doubts make the idea yours? Then use these as follow-ups, not a list to work through: - What triggered this — a conversation, a bug, a result, an annoyance? The trigger, not the topic. - Picture one reader. What do they already know, and what should