discuss-change

# Discuss Change Escalate open decisions, agree on the implementation shape, then implement. ## Task Tracking Use `TaskCreate` to create a task for each step: 1. Capture the task 2. Escalate product decisions 3. Deep-dive discussion 4. Confirm the shape 5. Run `/implement` skill ## Step 1: Capture the Task Absorb the request without interrupting. Take the task from the user's request, or from conversation context when the task was already established. Restate the goal in one or two sentences and confirm. ## Step 2: Escalate Product Decisions Identify product or design decisions the request did not resolve. Escalate these via `AskUserQuestion` before any code is written. Read the code the change would touch before judging whether a bullet matches. **Skip** when no bullet below matches the change. **Escalate when:** - The change requires choosing between user-facing behaviors the request did not specify (opt-in vs opt-out, strict vs lenient, sync vs async) - The change assumes product requirements that were not stated - Design trade-offs affect UX or product direction rather than technical implementation - Multiple valid approaches exist and the choice is a matter of product preference, not technical merit - The change would introduce a pattern not yet established in this codebase, or follow one sourced from outside it - The change adds consistency or durability machinery (a lease, lock, queue, versioning scheme, or new persistent entity) that no stated requirement de...