Agent skill
peer-review-prompt-plan
Run prompt plan review using the codex CLI as an independent reviewer. Returns structured findings without applying fixes. Use when the user asks to "peer review my prompt plan", "get a second opinion on my prompts", "codex review my prompt plan", or "run codex on my prompts".
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/peer-review-prompt-plan
SKILL.md
Peer Review Prompt Plan
AI-powered prompt plan review via codex. Delegates to /codex-exec for an independent review of the prompt plan against its source spec.
Step 1: Identify the Prompt Plan
Determine the prompt plan to review:
- If prompt plan text was provided by the caller, use it
- If a file path was provided, read the file
- If neither was provided, check for a prompt plan at
.turbo/prompts.md
Also read the source spec (path listed in the prompt plan's Source: field).
Step 2: Run /codex-exec Skill
Run the /codex-exec skill in read-only mode with the full prompt plan text, the source spec, and these review instructions:
Review the following prompt plan against its source spec. Check for: (1) spec requirements not covered by any prompt, (2) dead ends where a prompt creates something no later prompt consumes, (3) missing prerequisites where a prompt assumes something no prior prompt creates, (4) duplicated requirements across prompts, and (5) incorrect dependency ordering. For each issue found, state: the problem, which prompt(s) are affected, the impact, a suggested fix, and priority: P0 (spec requirement missing or system broken), P1 (significant gap), P2 (moderate issue), or P3 (minor improvement). Ignore stylistic preferences. If no issues are found, state that the prompt plan looks sound.
Step 3: Return Findings
Return the codex review output. The caller determines what to do with the findings.
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?