Codex implementation

Skill Studio-Moser/skills-n-stuff/plugins/pm/skills/codex-implementation

Product research, market intelligence, and content tools for AI-native teams

Install

npx -y skills add Studio-Moser/skills-n-stuff --skill codex-implementation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Ask the Codex CLI (running whatever model it's configured with) to implement a bounded, well-specified change in the repo. This is how the Codex model is invoked for implementation work. Use when the model-selection rubric routes bulk or mechanical implementation to Codex, when the user asks Claude to have Codex implement something, or when a parallel implementation agent should produce a patch in a worktree. For work Claude should own directly, implement it yourself instead.

SKILL.md

3.3 KB, as published. Nobody here has run it

Codex Implementation

Optional cross-vendor executor. Requires the OpenAI codex CLI. If command -v codex fails, this skill isn't available on this machine — say so and implement natively instead. The model-orchestration doctrine (references/model-orchestration.md) routes here only when the CLI is present.

Use Codex for bounded, clearly specified implementation work — typically in a worktree or from a parallel implementation agent producing a patch. Do not let Codex commit, push, deploy, or edit global config unless the user explicitly asked for that.

Workflow

Pin the current state with git status --short and note any user changes already present.
Define the implementation scope: files or behavior to change, files to avoid, constraints, and verification commands.
Create a temporary artifact directory for Codex's report.
Run codex exec with repo write access.
After Codex exits, inspect git status and git diff.
Run the cheapest reliable verification yourself when practical.
Report what Codex changed, what Claude verified, and any remaining risks.

Use this command shape:

ARTIFACT_DIR="$(mktemp -d "${TMPDIR:-/tmp}/codex-implementation.XXXXXX")"
REPORT="$ARTIFACT_DIR/report.md"
PROMPT="$ARTIFACT_DIR/prompt.md"

# Write a self-contained prompt to $PROMPT, then run:
codex exec \
  -C "$PWD" \
  -s workspace-write \
  - < "$PROMPT" > "$REPORT"

Example Prompt

Artifact directory: /tmp/codex-implementation.XXXXXX

Goal:
- Add keyboard navigation to the command palette.

Acceptance criteria:
- ArrowUp and ArrowDown move the highlighted item.
- Enter selects the highlighted item.
- Escape closes the palette.
- Existing mouse behavior keeps working.

Constraints:
- Preserve unrelated user changes.
- Do not commit, push, deploy, or edit global config.
- Follow existing component and test patterns.
- Reuse existing code and platform features; shortest working diff; no speculative abstractions.

Verification:
- Run the focused component tests if available.
- Otherwise run the nearest relevant typecheck or test command and explain the choice.

Report:
- Files changed
- Behavioral summary
- Verification run and result
- Anything blocked or uncertain

Keep prompts simple and self-contained. Codex is not Claude: it does what you tell it and little more, so state the goal, constraints, and verification plainly and skip elaborate persona or process instructions.

Review After Codex

Always inspect Codex's diff before telling the user the work is done. Revert only Codex-created mistakes when you are sure they are not user changes. If Codex leaves the repo in a worse state or changes unrelated files, stop and report the issue with the diff summary.

If codex is not installed or the command fails, report the error and offer to implement the change directly instead.