メニュー
Use after spec-writer to surface ambiguities or gaps in the active feature's spec.md as explicit questions, then update the spec in place once answered.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | clarify |
| description | Use after spec-writer to surface ambiguities or gaps in the active feature's spec.md as explicit questions, then update the spec in place once answered. |
When: right after spec-writer produces a draft spec, before plan-writer starts architecting against it. Re-run any time the spec is reopened and feels ambiguous.
Template: none — this skill operates on the existing spec, it does not fill a fresh template.
Output: specs/<active-feature>/spec.md (edited in place; same file, no new file created).
Steps:
.specify/state (fallback: newest dir under specs/).specs/<active-feature>/spec.md in full.User Stories, Requisitos Funcionais, Critérios de Aceitação, Fora de Escopo), list concrete ambiguities, missing edge cases, or contradictions as numbered questions.spec.md directly to resolve each ambiguity — tighten requirements, add missing acceptance criteria, or move newly-excluded items into "Fora de Escopo".status untouched (still draft) unless the human explicitly approves it elsewhere.Next: plan-writer.
Ingest a raw source into the project's OKF knowledge bundle — distill it into concept pages, refresh the index, and log the change. keel's compounding "LLM wiki" loop.
Use when implementation is complete, gates pass, and you need to decide how to integrate the work — presents structured options (merge, PR, keep, discard) and handles the chosen workflow, including worktree cleanup. Closes the SDD cycle after review-and-simplify.
Use when executing implementation plans with independent tasks in the current session
Orchestrates the implement-feature, evaluator, fix-runner loop for the active feature until all Criterios de Aceitacao are met and quality gates are green.
Use after the plan is approved to break the active feature's plan into a concrete task checklist, written into specs/<feature>/tasks.md from the tasks template.
Use while implementing a feature that has retries, queues, background jobs, external calls, or any critical path an on-call engineer will need to reason about in production. Invoke when adding a new endpoint, dependency, or async flow, and before considering such a feature done — instrumentation is developed alongside the code, like tests, not bolted on after.