aftercare

Use when the user wants to operate a post-build cleanup queue through natural language: initialize Aftercare in a repo, add/list/show tickets, recommend or start the next task, reorder work, reopen a ticket after failed acceptance, manage mixed fix/test/review/deploy work in one queue, run the queue loop, or sync queue summaries back into project memory. Works well for artifact-heavy build workflows, including roadmap-driven, spec-driven, pipeline-driven, and hybrid projects.

Use when the user wants to operate a post-build cleanup queue through natural language: initialize Aftercare in a repo, add/list/show tickets, recommend or start the next task, reorder work, reopen a ticket after failed acceptance, manage mixed fix/test/review/deploy work in one queue, run the queue loop, or sync queue summaries back into project memory. Works well for artifact-heavy build workflows, including roadmap-driven, spec-driven, pipeline-driven, and hybrid projects.

Add an Aftercare ticket explicitly. Use when the user invokes $ac-add or /ac-add, or wants a direct command-style way to add a fix, test, review, or deploy ticket to the queue.

Block an Aftercare ticket explicitly. Use when the user invokes $ac-block or /ac-block, or wants a direct command-style way to mark a ticket blocked.

Cancel an Aftercare ticket explicitly. Use when the user invokes $ac-cancel or /ac-cancel, or wants a direct command-style way to cancel a ticket.

Defer an Aftercare ticket explicitly. Use when the user invokes $ac-defer or /ac-defer, or wants a direct command-style way to defer a ticket.

Complete an Aftercare ticket explicitly. Use when the user invokes $ac-done or /ac-done, or wants a direct command-style way to mark a ticket done.

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.

Show the Aftercare command surface explicitly. Use when the user invokes $ac-help or /ac-help, or wants the explicit command list, minimal paths, and routing entry points.

Initialize Aftercare explicitly. Use when the user invokes $ac-init or /ac-init, or wants a direct command-style way to create the .aftercare runtime in the current repo.

List the Aftercare queue explicitly. Use when the user invokes $ac-list or /ac-list, or wants a direct command-style queue view without routing through the generic skill.

Pick the next Aftercare ticket explicitly. Use when the user invokes $ac-pick-next or /ac-pick-next, or wants the next candidate without claiming it.

Reopen an Aftercare ticket explicitly. Use when the user invokes $ac-reopen or /ac-reopen, or wants to send a finished ticket back into the queue because acceptance failed on the same issue.

Run the Aftercare loop explicitly. Use when the user invokes $ac-run-loop or /ac-run-loop, or wants a direct command-style way to keep running until the queue is empty or blocked.

Run the next Aftercare ticket explicitly. Use when the user invokes $ac-run-next or /ac-run-next, or wants a direct command-style way to execute the transitional run-next helper.

Show one Aftercare ticket explicitly. Use when the user invokes $ac-show or /ac-show, or wants a direct command-style way to inspect a specific ticket.

Start an Aftercare ticket explicitly. Use when the user invokes $ac-start or /ac-start, or wants a direct command-style way to claim a ticket.

Summarize Aftercare state explicitly. Use when the user invokes $ac-summary or /ac-summary, or wants a direct command-style summary of current queue state.

Sync Aftercare summary back into project memory explicitly. Use when the user invokes $ac-sync or /ac-sync, or wants a direct command-style way to regenerate the project summary output.