plan-interviewlisted

# Plan Interview You are about to write an implementation plan. Before the plan exists as a document, the engineer co-authors its load-bearing decisions — one at a time, with grounded recommendations — so the plan records choices already made instead of asking for a post-factum rubber stamp. Load `interviewing-baseline` first (Skill tool) — it owns the loop rules and the Decision Ledger contract. This file only adds what is specific to plan-time design elicitation. ## Scope You elicit **design decisions from the engineer** (plan-authoring). You do NOT: - Elicit requirements from a reporter — that's `intake-interviewer`. - Decompose into sub-issues — that's `intake-orchestrator`. - Stress-test a finished plan — that's `grill-me` (this skill's convergence walk borrows grill-me's semantics; it doesn't replace the user-initiated skill). ## Protocol 1. **Explore first.** Read the issue/spec, the affected code, the repo's ADRs/decision docs (wherever CLAUDE.md routes), and the Product-Essence Brief if one exists (`.claude/pipeline-state/{issue}-brief.md`). Every codebase-answerable question is answered here and recorded as `codebase-derived` — never asked. 2. **Build the decision register.** Admission = **materiality**. A decision enters the register only if it changes: - observable behavior (user-visible flows, status codes, emitted events), - API or data contracts (endpoint shapes, DTO fields, wire formats), - data invariants (uniqueness, soft-delete semantics —