메뉴
Use when the user says resume, continue, or pick up where we left off, starts a new session on an existing Agent-Agile project, or is recovering after a crash or context reset, for example "/aa-resume", "let's continue", "where were we".
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when the user has an existing plan, PRD, or spec document they want brought into this planning system instead of a fresh grill and intake — or invokes /aa-import with a path or description of that document.
Use when the user wants to plan a new project from a clear idea, has already locked an idea with aa-grill, or invokes /aa-new-project.
Use when multiple epics should run back to back without a human kicking off each one by hand, or the user invokes /aa-autopilot [--gate full-auto|checkpoint].
Use when the current epic on the roadmap is done and the next pending epic needs to be sliced into worker-ready story cards, or the user invokes /aa-plan-epic.
Use when the user wants to review a finished epic's demo, decide whether to approve, redo, or replan an epic, or invokes the review gate, for example "/aa-review", "let's review this epic", "walk me through the demo", "I want to give feedback on this epic".
Use when a sliced epic (story cards already written) is ready to build, or the user invokes /aa-execute-epic.
| name | aa-resume |
| description | Use when the user says resume, continue, or pick up where we left off, starts a new session on an existing Agent-Agile project, or is recovering after a crash or context reset, for example "/aa-resume", "let's continue", "where were we". |
| license | MIT |
| metadata | {"system":"agent-agile"} |
Resolve the Agent-Agile playbook root: use the first of these that exists — (1) ${CLAUDE_PLUGIN_ROOT}/playbooks, (2) ./.claude/agent-agile/playbooks, (3) ./.agents/agent-agile/playbooks, (4) ~/.claude/agent-agile/playbooks, (5) ~/.agents/agent-agile/playbooks, (6) ./playbooks.
Read playbooks/execution.md's "Resume protocol" section from that root, and follow it exactly:
.planning/STATE.md does not exist, no project has been started here yet. Say so plainly, and point the user at the three front doors instead of guessing at a state that isn't there: a vague spark → /aa-grill, a clear idea → /aa-new-project, an existing plan or spec → /aa-import..planning/STATE.md first and only. Don't re-derive status by re-reading the whole epic history — STATE.md is the baton, kept small on purpose so this step stays cheap every time.STATE.md says the run is: the phase it names (grill, intake, panel, prereqs, an epic's wave, review, or done), the "Now" sentence, and the "Next" sentence.STATE.md names a blocker, resolve or surface that blocker before doing anything else — never work around it silently.Close the session, without exception, with one STATE.md update: what's in progress, what's next, the pointers the next session needs, and any blocker. A session that stops without this update leaves the next session to reconstruct state from scratch — the entire point of the baton is that this never has to happen.