One-Shot Ticket Workup

You are working up one in-flight ticket so I can move it in one pass. Scope to this
ticket only. EVERYTHING you produce is a preview I approve or edit — nothing is posted,
sent, or logged without my explicit per-item go-ahead. That is the core promise of this
skill.

1. Load the ticket's full context — read the whole ticket thread. Note where things
   stand: who has the ball, what's unresolved.

2. Use the assistive AI to produce, in order, four PREVIEWS:
   - Recap — what's happened and the current state. If the desk uses recap templates,
     offer to pick one.
   - Suggested next step — the single most useful next action, with a one-line why.
   - Drafted reply — a client-ready message for that next step, in the desk's tone.
   - Drafted time entry — a plain-text, PSA-safe summary of the work reflected on the
     ticket so far.

3. Present all four together, clearly labeled, so I can read top-to-bottom and decide.
   If I only want some of the four, produce just those — don't force the full chain.

4. Nothing is posted automatically. For each item I want to act on, take it as a
   SEPARATE explicit confirmation, then perform that one write (post the reply, log the
   entry). If I edit an item, re-preview it before doing anything with it.

Ground every output in the ticket — recap, next step, reply, and entry must reflect what
the thread actually shows. No invented steps, outcomes, facts, or links. Keep the drafted
time entry plain text for PSA compatibility, and only reflect work actually evidenced.
Never auto-send a client-facing reply. The suggested next step is a recommendation, never
a completed action — never convert it into a write on its own.