メニュー
Use for prototype, MVP, fullstack feature, from-scratch feature, or multi-domain work that needs a SPEC.md before planning or implementation. Do not use for tiny one-file edits.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use for UI, frontend, styling, landing page, or component creation; injects palettes, typography, layouts, motion, and anti-generic design rules.
Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.
Use for frontend, backend, mobile, debugging, security, or specialized engineering work that needs focused domain references and strict boundaries.
Use when an approved plan has independent tasks ready for delegated execution with fresh subagents and two-stage review.
Use before completion, PR, deploy, handoff, or when verifying code changes. Runs advisory or blocking checks and reports evidence.
Use when the task involves reading, creating, or editing `.docx` documents, especially when formatting or layout fidelity matters; prefer `python-docx` plus the bundled `scripts/render_docx.py` for visual checks.
| name | codex-spec-driven-development |
| description | Use for prototype, MVP, fullstack feature, from-scratch feature, or multi-domain work that needs a SPEC.md before planning or implementation. Do not use for tiny one-file edits. |
| load_priority | on-demand |
Use before $prototype, MVP, fullstack, or high-ambiguity feature work. Write .codex/specs/<slug>/SPEC.md first, then plan, delegate, implement, and validate against acceptance criteria.
$spec, $prototype, "spec-driven", "MVP", "fullstack prototype", "from scratch", or "build whole app".Schema-Version: 1.0, AC IDs such as AC-001, and a traceability table mapping changed files to AC IDs and validation commands..codex/specs/; do not always load every spec.check_spec.py after code changes when .codex/specs/ exists.python "<SKILLS_ROOT>/codex-spec-driven-development/scripts/init_spec.py" --project-root <path> --title "<title>"
python "<SKILLS_ROOT>/codex-spec-driven-development/scripts/check_spec.py" --project-root <path> --changed-files <csv>
init_spec.py returns JSON with status, spec_path, and slug.check_spec.py returns JSON with schema_version, overall, matched_specs, matched_acceptance_criteria, unmapped_files, and suggested_actions.$hook to detect domains and readiness.$init-profile if profile is missing.$genome and $init-docs if context/docs are missing.$spec to lock requirements and acceptance criteria.$plan, then $sdd or inline execution.$check-full and update role docs/handoff.references/spec.schema.json: required spec markdown contract and traceability fields.