メニュー
Use this skill after execution approval for implementation work in an approved chat-only or task-file task. It governs implementation-time routing, canonical task updates, and the final review checkpoint.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Mandatory only on the task-file path of `spec-loop-plan-task`. Use when an active task file already exists and the next user-facing action would otherwise present task-file work for evaluation, feedback, review, or execution approval.
Choose the planning form for new work and plan it before execution. Use this skill to decide whether the work is taskless, chat-only, a task file, a task file with subtasks, or multiple task files / backlog items, and to create the needed plan for non-trivial implementation work or investigation work that needs its own task.
Optional skill. Reconstruct a human-review-preparation file from an existing pull request, merge request, branch diff, or commit range in a repository the user trusts. Use when the user wants retrospective understanding of already-implemented changes, AI-side assessment and recommendations, and an optional provider-specific sharing variant written to a local file when needed.
Create or update a project glossary in the Spec Loop AsciiDoc glossary format. Use when the user, project instructions, or `spec-loop-plan-task` already requires project glossary work. This skill is mandatory for AsciiDoc project glossaries unless the user explicitly opts out for the current project or session.
Engage the User to resolve important open decisions in Spec Loop work, including tasks, plans, design updates, work breakdowns, implementation checkpoints, and ADR drafting. Use when the user asks to clarify, compare options, discuss criteria, or stress-test, or when different answers could materially change scope, behavior, policy, constraints, route, Design, Test specification, or ADR content. Provides mandatory decision screening for workflows that require it before dependent Spec Loop content is written or revised. Also use for general grilling when explicitly selected.
Create or revise file-based Spec Loop work breakdown artifacts for task-file work that uses subtasks or multiple task files / backlog items.
| name | spec-loop-implementation-flow |
| description | Use this skill after execution approval for implementation work in an approved chat-only or task-file task. It governs implementation-time routing, canonical task updates, and the final review checkpoint. |
Use this skill after execution approval for implementation work in an approved chat-only or task-file task.
If no approved active task exists, return to spec-loop-plan-task/SKILL.md.
review.Implementation notes
check.spec-loop-plan-task bundle, stop and ask the User
which rules should govern.Keep using the approved active task as the source of truth. Edit the active task file or canonical chat-only task only when the shared core and the active path companion allow it.
implementation-flow-guidance.md defines the route rules, when
canonical task sections may change, the meaning of review,
Implementation notes, and the completion checklist.
The path companion defines the active path mechanics, including
chat-only recovery or promotion or the task-file move into review.
If the current increment is unclear, do not use this skill. Return to spec-loop-plan-task/SKILL.md.