Force one Aftercare ticket to become the next queued item. Use when the user invokes $ac-force-next or /ac-force-next, or wants a direct command-style way to promote one ticket to the front without preempting active work.
Installation
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Force one Aftercare ticket to become the next queued item. Use when the user invokes $ac-force-next or /ac-force-next, or wants a direct command-style way to promote one ticket to the front without preempting active work.
ac-force-next
Read ../aftercare/SKILL.md first and follow its runtime resolution and queue rules.
Treat all user text after $ac-force-next or /ac-force-next as ticket-id context.
Use an explicit queued ticket id whenever available; if no ticket id can be recovered, explain that this explicit command needs one.
Run force-next <id>.
Explain that this is non-preemptive: it changes the next queued candidate but does not interrupt the current active ticket.
Return the forced ticket id, its status, and the current active ticket if one exists.