Prompt to update ticket after refine-plan results in changes

[williamthorsen]

Context

When /refine-plan produces a revised plan that changes the solution approach (e.g., build-time flag → runtime domain matching), the associated ticket description and acceptance criteria may become stale. Currently, the skill does not prompt the user to update the ticket after the revision is complete.

Example

In a COMPPLAN-277 refinement, the plan changed from a VITE_USER_SWITCHING_ENABLED build-time flag to runtime hostname detection. The ticket still referenced "build-time flag", "deploy script env var", and "production builds" (instead of "production environments"). This was caught only because the user asked about it.

Proposal

After a successful plan revision that results in material changes, the /refine-plan skill should:

1. Compare the revised plan's approach/solution with the ticket's solution section
2. If they diverge, prompt the user: "The revised plan changes the solution approach. Would you like me to update the ticket to match?"
3. If yes, update the ticket file (and optionally the Jira issue if linked)

This could be a simple heuristic check in step 6 (Report completion) of the refine-plan skill.

Could be combined with #320

[williamthorsen]

Folded into #320 — the ticket-update prompt after refine-plan is now part of the broader next-steps resumption prompt work.