From grimoire
Plans and conducts journalistic interviews to maximize source cooperation and information yield. Useful for reporters and investigators preparing structured interviews.
How this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:design-interview-strategyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Plan and execute a structured journalistic interview that builds trust, extracts accurate information, and generates usable quotes.
Plan and execute a structured journalistic interview that builds trust, extracts accurate information, and generates usable quotes.
Adopted by: IRE (Investigative Reporters and Editors), SPJ, Columbia Journalism School, and professional investigative teams at ProPublica, NYT Investigations, and the Washington Post. Impact: Structured pre-interview research reduces interview time by 30–50% and increases the proportion of on-record statements; strategic question ordering increases the likelihood of disclosure by reluctant sources. Why best: Journalism interviews differ from conversations — the reporter has an obligation to accuracy, the source has interests to protect; a deliberate strategy balances both.
Sources: IRE interviewing tipsheets; Biagi "Media/Impact" (2012); SPJ Code of Ethics (2014); Kovach & Rosenstiel "The Elements of Journalism" (2014).
Define interview goals — list the 3–5 specific facts or quotes you need. Distinguish must-have from nice-to-have before scheduling.
Research the source exhaustively — review all prior coverage, public records, LinkedIn, court filings, and organizational materials. Never ask questions answerable through public records.
Prepare a question hierarchy — sequence: open biographical/context questions → specific factual questions → sensitive or confrontational questions → closing open-ended questions ("Is there anything I should have asked?").
Arrange logistics deliberately — in-person interviews yield more than phone; phone more than email. Record with consent (check state laws). Confirm the time, location, and scope in writing.
Establish ground rules up front — clarify on-record vs. off-record vs. on-background at the start, not mid-conversation. Define each term explicitly to avoid misunderstanding.
Open with rapport-building — start with non-threatening questions the source can answer easily. Silence is a tool; let pauses breathe.
Ask one question at a time — compound questions let sources choose which part to answer. Listen for evasions and follow up precisely.
Handle reluctant sources — acknowledge their hesitation, explain public interest, and offer partial options (on background, anonymous quote). Never mislead about the story's nature.
Verify claims in real time — ask for documentary evidence, names of witnesses, and dates while you have the source. Don't rely solely on memory or single-source claims.
Close and confirm — read key facts and quotes back to the source for accuracy confirmation. Provide a callback number; ask if they want to add anything.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireGenerates interview questions matched to a subject's background, public record, and story angle, with a structured format for high-stakes journalism.
Prepares hypothesis-driven user interview guides based on Teresa Torres, Rob Fitzpatrick, Bob Moesta, and Cindy Alvarez. Runs live or imports from Granola, extracts signal into FEEDBACK.md.
Provides frameworks for discovery, validation, usability, and generative user interviews with question scripts, techniques, and analysis for product research.