conceptualizelisted

# Conceptualize Interview relentlessly until shared understanding is reached, then leave a compact Conceptualize handoff under the selected artifact root: `.planning/<concept-slug>/index.md` plus at least one focused Slice Markdown file with stable commitments. Source inspection still uses the active code root/worktree. The eager workflow should be enough to guide the session. Load references only at the step where their rules are required; do not preload references merely because they are named. ## Always - Ask one focused question at a time; never dump a multi-question interrogation block. - For each material question, provide your recommended answer and tradeoff-shaped options when useful. - Inspect the repo instead of asking when repo evidence can answer; ask only for remaining intent, preference, or risk acceptance. - Continue the loop until shared understanding is sufficient for implementation planning without inventing behavior. - Before settling a material Module/Interface design branch, apply the shared codebase-design model and right-sized-complexity rule: identify the owning Module, full caller Interface, Seam, justified Adapters, Depth/Leverage/Locality, and deletion-test result. Skip this ceremony when no material Module/Interface decision exists. Choose the smallest complete safe design; every extra state, abstraction, dependency, or branch needs a named requirement/risk or must be cut, without removing required validation, failure handling, or verif