implement-spec-with-codex
/implement-spec-with-codex
Run [implement-spec](../implement-spec/SKILL.md) with Codex doing the implementation passes while you orchestrate, integrate, and review. Use when the user asks to implement a spec with Codex, or to run implement-spec with Codex as the implementer.
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 21.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Run [implement-spec](../implement-spec/SKILL.md) with Codex doing the implementation passes while you orchestrate, integrate, and review. Use when the user asks to implement a spec with Codex, or to run implement-spec with Codex as the implementer.
Original author description
Run [implement-spec](../implement-spec/SKILL.md) with Codex doing the implementation passes while you orchestrate, integrate, and review. Use when the user asks to implement a spec with Codex, or to run implement-spec with Codex as the implementer.
How it works
- Role split
- Rules
SKILL.md preview
--- name: implement-spec-with-codex description: Run [implement-spec](../implement-spec/SKILL.md) with Codex doing the implementation passes while you orchestrate, integrate, and review. Use when the user asks to implement a spec with Codex, or to run implement-spec with Codex as the implementer. --- # Implement Spec with Codex Run [implement-spec](../implement-spec/SKILL.md) exactly — same loop, same gates, same maintenance checkpoints — but Codex writes the code. Invoking this skill IS the explicit ask that authorizes `codex exec` delegation under the [codex](../codex/SKILL.md) skill. ## Role split - **Codex implements — whenever possible.** Default every implementation pass to a `codex exec`, sliced sharp and prompted per the codex skill (prompt blocks, sandbox choice, exec liveness). Run independent slices as concurrent execs in separate worktrees, exactly where implement-spec would fan out subagents. - **You orchestrate and review.** The spec loop stays yours: pick the next slice, reconcile plan with code, author each prompt end-to-end, integrate diffs, run the gates, review the merged tree, commit, update the handoff, run maintenance checkpoints. None of that delegates. Keep a pass yourself only when slicing it sharply would cost more than doing it — tiny fixups, plan reconciliation, integration conflicts. ## Rules - You own every result: read the full diff and run the verification yourself. "Codex says it's done" is never done. - Visual results carry implement-spec's two extra proofs (production-route pixel diff + unprimed critique) with double force here: a sandboxed Codex never saw its change render, so a pass that misses the production render path entirely arrives looking fully "verified". - A sandboxed Codex ships code it never saw run — browser-verify every visual slice yourself and budget fix rounds. Send a red gate back as a resumed follow-up with the failing evidence; fix it yourself only when that's smaller than re-prompting. - Commit hygiene stays yours: review the change list of the merged tree before every commit, exactly as implement-spec demands of the integrating reviewer.
Versions
The database has no other skills named implement-spec-with-codex.
Database snapshot: 13.11.2026 · package version 0ba3323c2c8a (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 86implement-spec
Implement a specification in code. Use when the user wants to implement the result of /mattpocock:to-spec and /mattpocock:to-tickets, or asks to work a whole spec on one integration branch. - 82implement-spec
Execute an approved spec's tasks.md test-first, one task per commit, with review subagents. Use when the user asks to implement or continue a spec. - 95implement
Implement a piece of work based on a spec or set of tickets. Use when an agreed spec or ticket set should now be built. Triggers on: implement, build this spec, work these tickets. - 81implement
Implements a piece of work from a spec or ticket set. Use when the user says \"implement this spec\", \"work the tickets\", or wants code written from an existing plan. - 90om-auto-implement-spec
Implement an existing spec and ship a verified, reviewed, ready PR. Resolves the spec by path, name, issue, or spec-PR number (clean stop with candidates when not found). A spec PR stays design-only — implementation ships on its own PR referencing it. Delegates to… - 84implement-spec
Orchestrate implementation of spec-workflow tasks. Use when user says "implement the spec", "execute spec tasks", "run the spec workflow", "implement spec-name tasks", or needs to coordinate agent execution for spec-workflow documents.