メニュー
Use after the PRD exists to write the functional spec for the active feature into specs/<feature>/spec.md from the spec template, with status:draft frontmatter.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | spec-writer |
| description | Use after the PRD exists to write the functional spec for the active feature into specs/<feature>/spec.md from the spec template, with status:draft frontmatter. |
When: PRD done, before planning.
Template: .specify/templates/spec-template.md.
Output: specs/<active-feature>/spec.md.
Steps:
.specify/state (single line, e.g. 001-name); if absent, fall back to the newest directory under specs/..specify/templates/spec-template.md to specs/<active-feature>/spec.md.status, feature, date) and each section that exists in the template:
User Stories — story + acceptance criterion per story.Requisitos Funcionais — numbered functional requirements (RF1, RF2, ...).Critérios de Aceitação — Given/When/Then scenarios.Fora de Escopo — what this spec explicitly excludes, plus known dependencies.status: draft in the frontmatter — do not set it to approved yourself.Approval: the spec is "approved" only when a human flips the frontmatter to status: approved. The phase-gate hook (core/claude/hooks/phase-gate.mjs) enforces this — it blocks code edits until both spec.md and plan.md carry status: approved.
Next: clarify, then plan-writer.