菜单
Show status overview and next steps for an .aiwork/ spec. Use when user says "next steps", "what's left", "status", "progress", or wants to see what's planned, unplanned, or incomplete for a task.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Implement work from a ticket, spec, or inline description; auto-detects the next item from the task folders when no argument is given.
Scan current directory (recursively) for Claude Code skills, slash commands, agents, hooks, and plugin/MCP configs, then render an interactive HTML graph of their explicit and implicit relationships. Use when the user says "skills map", "skill graph", "visualize skills", "map skills", "how do my skills relate", or wants to audit a skill collection before publishing.
Turn the current conversation context into a spec. Use when user wants to create a spec (or PRD) from the current context.
Break a plan, spec, or the current conversation into vertical-slice tickets, each declaring its blocking edges.
Structure AI work artifacts under .aiwork/{YYYY-MM-DD}_{slug}/ folders using the project's protocol (triage, research, spec, prd, plan, review, notes, docs/). Use when the user asks to plan, make a spec, triage, research a task, write a report, code review, summarize findings, save the work, document decisions, record this, write that down, persist findings, or references any path under .aiwork/. Also use when starting a non-trivial task that needs a plan or spec before implementation, or when finishing one and capturing notes.
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
| name | next-steps |
| description | Show status overview and next steps for an .aiwork/ spec. Use when user says "next steps", "what's left", "status", "progress", or wants to see what's planned, unplanned, or incomplete for a task. |
| allowed-tools | Read, Glob, Grep |
| argument-hint | ["spec-or-task-folder-path"] |
Show a status overview for an .aiwork/ task. Follows the aiwork-protocol skill.
Arguments ($ARGUMENTS): Optional path to a spec file or task folder. If omitted, find most recently modified .aiwork/*/.
.aiwork/*/Read the spec and all plan files in the folder. For each step in the spec's implementation order:
plan_N.md?status:? (draft / active / complete / superseded)[x] or [ ]?If a tickets/ subfolder exists, also read each ticket's frontmatter: status (ready / in-progress / done) and blocked_by. The frontier is every ready ticket whose blockers are all done.
Keep output brief. Print:
-), status; for tickets include blockers/implement (naming the frontier ticket if tickets exist) or "all done"