메뉴
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.
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.
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.
| name | ac-start |
| description | 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. |
../aftercare/SKILL.md first and follow its runtime resolution and queue rules.start <id>.pick-next first and then start <id> when safe.