Grilling flow skips /to-spec or /to-task and starts implementation directly

## Problem After a `/grill-with-docs` session reaches a confirmed shared understanding, the workflow can jump directly into implementation instead of routing through the appropriate next skill. ## Reproduction 1. Invoke `/grill-with-docs` for a repository change request. 2. Let the grilling interview establish and confirm the design decisions. 3. Confirm the final implementation contract. 4. Observe the next action. ## Actual behavior The agent started an implementation sub-agent immediately after confirmation. In this case, the user intended a specification/issue workflow, but implementation began before `/to-spec` or `/to-task` was invoked. The user then had [x] stop the session to invoke `/to-spec` manually. ## Expected behavior After grilling reaches a confirmed shared understanding, the workflow should route based on the user’s intent before any edits or implementation delegation: - Use `/to-spec` for a specification or issue-writing request. - Use `/to-task` for an implementation task. - If intent is still ambiguous, ask the user which handoff they want. No implementation agent, file edit, commit, or other execution should start before that handoff is selected. ## Impact This skips the intended planning/specification gate, can create unrequested code changes, and makes the transition from design conversation to execution unpredictable. ## Suggested fix Update the grilling completion behavior and/or skill handoff instructions so that confirmation terminates grilling with an explicit intent-routing step. Preserve the confirmed design tree as context for `/to-spec` or `/to-task`, but do not treat confirmation alone as authorization to implement.