talk-it-throughlisted

# Talk It Through Reach shared understanding without applying the same interview depth to every question. Do not implement the feature. Inspect facts, resolve decisions one at a time, and keep durable wayfinding state out of this skill. ## Invocation contract Choose the mode from the caller, never by asking the user to classify it. ### Standalone mode Use for a direct request to discuss, explore, shape, or prepare bounded work. Resolve the planning thread and load `write-planning-brief` when it is ready to become durable planning input. If the effort is too foggy or large for one planning context, establish only enough to explain why a multi-session map is warranted. Recommend explicit invocation of `/skill:map-it-out start <initiative>` and stop without creating a competing map or brief. If the user declines `map-it-out` and explicitly requests a snapshot, write a `More decisions required` brief. ### Embedded-decision mode Use only when a caller such as `map-it-out` explicitly supplies one decision or question, its destination, known context, resolved dependencies, constraints, and expected output. Resolve only that question and return a structured result to the caller. In embedded mode, never: - create or update a wayfinding map or decision record; - choose the next decision or manage dependencies, frontier, fog, claims, or scope state; - invoke `write-planning-brief`, `to-plan`, or another implementation workflow; or - persist the result except for a research, de