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.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
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.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work — guides completion of development work by presenting structured options for merge, PR, or cleanup
The English summary is being prepared. Showing the original description.
Use when a project has 50+ files, missing context, or explicit $codex-genome request; generates multi-layer project context to reduce hallucination.
The English summary is being prepared. Showing the original description.
Use for DESIGN.md visual identity contracts; author, scaffold, lint, diff, and export design contracts with the upstream spec and CLI.
The English summary is being prepared. Showing the original description.
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.
The English summary is being prepared. Showing the original description.
Use when code changes may require documentation updates; maps git diff to candidate docs without auto-editing documentation.
The English summary is being prepared. Showing the original description.
Use for documents, reports, memos, guides, academic papers, or formal text that needs clear structure, reliable tone, formatting, and diagrams.
The English summary is being prepared. Showing the original description.