AgentStack
SKILL verified MIT Self-run

Consulting Codex

skill-raccrompton-claude-codex-skills-consulting-codex · by raccrompton

Use to get a Codex second opinion on a drafted spec or plan before it reaches the user's approval gate — invoked at the superpowers brainstorming spec-review gate and the writing-plans plan-approval gate. Read-only critique; iterates the artifact to convergence; returns a digest.

No reviews yet
0 installs
4 views
0.0% view→install

Install

$ agentstack add skill-raccrompton-claude-codex-skills-consulting-codex

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Consulting Codex? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Consulting Codex on a spec or plan

Get a second opinion from the local Codex CLI on a drafted spec or plan, iterate it to a stronger state, and hand back a digest. You (the agent) remain responsible for the edits and the judgment; the user remains the final gate.

Inputs

  • ARTIFACT — path to the drafted spec or plan doc.
  • TYPEspec or plan.

Procedure

  1. Build the review prompt for the TYPE:
  • spec: "Review the design spec at ``. Identify gaps,

ambiguities, contradictions, unstated assumptions, scope creep, missing error/edge cases, and simpler alternatives. Cite sections concretely. Do NOT rewrite — critique only. If it is solid, say so plainly."

  • plan: "Review the implementation plan at ``. Check task

ordering, hidden/implicit dependencies, missing steps, risky or untestable steps, and anything underspecified for an engineer with zero context. Cite tasks concretely. Do NOT rewrite — critique only. If it is solid, say so."

  1. Run Codex (read-only):

``sh codex exec --sandbox read-only --skip-git-repo-check '' `` The repo is readable, so Codex can ground its critique in surrounding code.

  1. Filter the critique using superpowers:receiving-code-review: verify each

point against the artifact and codebase. Incorporate the valid ones by editing ``. Reject wrong/over-engineered ones and record a one-line reason for each.

  1. Iterate to convergence: re-run step 2 on the revised artifact. Stop when

Codex raises nothing material OR after 3 rounds total.

  1. Return a digest (see Output).

Error handling — never block

If codex is missing from PATH, unauthenticated, exits non-zero, or a call exceeds ~120s: stop, emit Codex consult skipped: , and return control so the workflow proceeds to the user's gate. A missing/flaky Codex must never stall the workflow.

Output (the digest)

Return a short digest for the user's gate:

  • Raised: what Codex flagged (bulleted).
  • Incorporated: what was folded in.
  • Rejected: what was rejected and why.
  • Rounds: count, plus any items still open at the 3-round cap.

If Codex was clean on round 1: "Codex: no material issues." If skipped: the skip reason.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.