From pm-journalism
Prepares journalists for source interviews including hostile/accountability interviews. Produces sequenced question plans, ground-rules handling, techniques for evasive subjects, and capture plans.
How this skill is triggered — by the user, by Claude, or both
Slash command
/pm-journalism:source-interview-prepThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
A journalistic interview isn't a friendly chat or a research call — it's an on-the-record exchange where the subject may have every reason not to answer straight. This skill preps the interview to get truthful, usable, attributable answers: rapport first, the hard questions sequenced so they don't end the conversation early, and a plan for the dodge.
A journalistic interview isn't a friendly chat or a research call — it's an on-the-record exchange where the subject may have every reason not to answer straight. This skill preps the interview to get truthful, usable, attributable answers: rapport first, the hard questions sequenced so they don't end the conversation early, and a plan for the dodge.
Given the subject and the story, write the full prep — infer where the subject is cooperative vs. defensive and sequence accordingly. Always handle ground rules explicitly; never counsel deception or entrapment.
Ask for (if not provided, else infer and label):
On-the-record vs. background vs. off-the-record vs. not-for-attribution — define them, agree them up front, and note how you'll handle mid-interview attempts to go off-record.
Techniques for the evasive or hostile subject: the follow-up that closes the gap, repeating the unanswered question, using documents/quotes to press, silence, and staying neutral rather than arguing.
Recording (and consent/legal note — recording-consent laws vary by jurisdiction), notes, and how you'll verify quotes.
Guides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Resolves in-progress git merge or rebase conflicts by analyzing history, understanding intent, and preserving both changes where possible. Runs automated checks after resolution.
npx claudepluginhub mohitagw15856/pm-claude-skills --plugin pm-journalism