interview-handofflisted

Prepares an interview that someone else runs, then collects the result back. Grills the user until the design tree is exhausted, writes a handoff package into the project (the questions, a short context document, and a prompt), and later reads whatever that interview produced, matches every answer to its question, classifies it, flags anything that contradicts an earlier answer, and offers the next round from what is still open. Use when the user types /interview-handoff:run, /interview-handoff:collect, /interview-handoff:config, or says "prepare an interview", "I want to be interviewed about X elsewhere", "make a handoff for this", "collect the answers from that session", "analyse this transcript against my questions", or "run another round". Never runs the interview itself.
SashaMarchuk/claude-plugins · ★ 0 · AI & Automation · score 73

Install: claude install-skill SashaMarchuk/claude-plugins

# interview-handoff You prepare an interview and you collect its result. **You never conduct the interview.** Somebody else does that, somewhere else, against the files you write. Three modes: `--run`, `--collect`, `--config`. Read `## Step 0` before any of them. --- ## Step 0. Read the resolved config, always Do this before any other work, in every mode, including when the user only asked a question. Never skip it, and never offer a fast path that skips it. Read the merged configuration from these files, lowest to highest, later overriding earlier: ``` 1 <config-root>/shared/identity.json 2 <config-root>/shared/plugins/interview-handoff.json 3 ./.claude/shared/identity.json 4 ./.claude/shared/plugins/interview-handoff.json 5 ./.claude/shared/identity.local.json 6 ./.claude/shared/plugins/interview-handoff.local.json ``` `<config-root>` is `$CLAUDE_CONFIG_DIR` when set, otherwise the home directory plus `/.claude`. Never write a literal `~` into a file call. Never touch `<config-root>/plugins/`, which belongs to Claude Code. **Running with no config at all is normal.** Do not fail and do not stall. Ask what you need at the moment you need it, use the answer, and write it down as configuration (`references/config.md` says which file each answer lands in). No setting is a precondition for running: a missing one is a question asked inline, never a stop. **Autopilot.** If the person says autopilot, or passes `--auto`, stop asking them about settings: reuse whateve