菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
| name | ac-block |
| description | 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. |
../aftercare/SKILL.md first and follow its runtime resolution and queue rules.in_progress, you may use that ticket.block <id> with the user's reason when present.