菜单
Use when the user asks for status, progress, an overview, "where are we", a roadmap summary, or Key Result progress on an Agent-Agile project, for example "/aa-status", "how's this project going", "what's left to do".
用 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-status |
| description | Use when the user asks for status, progress, an overview, "where are we", a roadmap summary, or Key Result progress on an Agent-Agile project, for example "/aa-status", "how's this project going", "what's left to do". |
| license | MIT |
| metadata | {"system":"agent-agile"} |
Read-only — never write to any file, never dispatch a subagent.
If .planning/STATE.md does not exist, say so and point the user at the three front doors: a vague spark → /aa-grill, a clear idea → /aa-new-project, an existing plan or spec → /aa-import.
Otherwise, render four sections in order, sourced from the files named:
.planning/ROADMAP.md and reproduce its epic table as-is: number, epic name, demo sentence, initiative served, and status..planning/STATE.md and summarize its fields in plain language: which phase the project is in, what's in progress now, what's next, and any blocker..planning/PROJECT.md's Key Results list and restate each one. For any Key Result whose progress is evidenced elsewhere on disk — a LEARNINGS.md note, a verified epic whose demo sentence maps onto it — note that evidence next to it; otherwise mark it as not yet measured. Never invent a number that isn't backed by something on disk..planning/PREREQS.md and list only the rows whose status is not verified (that is, pending or done) — a done row still belongs here, because "done" without "verified" means nobody has confirmed it actually works yet. If every row is verified, say so explicitly rather than showing an empty section.Present all four sections together as one status report; don't ask the user which section they want first.