메뉴
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.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
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.
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.
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-prepare-execution-approval |
| description | 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. |
This skill is mandatory only on the task-file path of the
spec-loop-plan-task workflow. It is not used for chat-only planning
path work kept in chat.
Before work: read spec-loop-plan-task/SKILL.md, follow all files it
requires, and apply the full spec-loop-plan-task bundle as shared
convention guidance. Then read
execution-approval-guidance.md.
Update the same active task file for user-facing review readiness. Do not create a second task artifact or a new pre-execution task status.
Use execution-approval-guidance.md as the authoritative source for readiness checks, diagram-first preparation, duplication removal, user-facing review gating, and approval-seeking output.
Follow execution-approval-guidance.md for the allowed user-facing outcomes and response rules.
If readiness checks find directly fixable task defects, update the active task in place and re-run the readiness checks before producing user-facing output, except for structural decomposition changes handled specially by execution-approval-guidance.md.
If readiness checks find issues that can be resolved from existing evidence, update the active task in place and re-run the readiness checks before producing user-facing output.
If readiness checks show that task-file compaction is needed, use spec-loop-compact-task-file/SKILL.md and then resume this skill.
If any important open decision remains and it is user-preference-sensitive, needed to choose the next path, or could materially change scope, constraints, design, or test specification, do not end with a blocker list. Invoke spec-loop-clarify-task/SKILL.md in the same turn, then resume this skill after clarification before seeking execution approval.
After task-file execution approval:
spec-loop-plan-task task-file
path: perform only the approved investigation, record final output in
Findings, satisfy any Test specification, and move the task or
subtask to review.If no active task file exists, if the current increment is unclear, or
if chat-only planning is in use, do not use this skill. Continue task
work under the spec-loop-plan-task bundle instead.