codex-spec-review

Review requirements documents for ambiguity, missing criteria, and contradictions.

Updated Jun 13, 2026
One-click install
npx skills add https://github.com/taloncjones/dotfiles --skill codex-spec-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-spec-review
Source: https://github.com/taloncjones/dotfiles/tree/main/claude/skills/codex-spec-review
Command: npx skills add https://github.com/taloncjones/dotfiles --skill codex-spec-review

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a second-model Codex review of finalized specifications or PRDs, identifying ambiguities, contradictions, missing criteria, and potential issues before any implementation plan is written.

Core Features & Use Cases

  • Codex Review: Utilizes a different Codex model to review requirements for clarity, completeness, and consistency.
  • Issue Identification: Surfaces potential problems like ambiguity, missing criteria, and contradictions.
  • Fix Incorporation: Proposes fixes to be folded back into the spec.
  • Use Case: After finalizing a spec/PRD, use this Skill to ensure the requirements are solid before proceeding to planning.

Quick Start

Run codex-spec-review to review the spec for ambiguities and propose fixes.

Frequently Asked Questions about codex-spec-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review software requirements for ambiguity and contradictions before planning?

A Codex spec review assumes no requirements are settled and requires access to your spec document, along with optional related context like design or product briefs, to perform an independent requirements analysis using a different Codex model.

Can I use a different Codex model to get a second opinion on a PRD?

To review a finalized spec, run codex-spec-review with the document and optional related context. The skill performs an independent requirements analysis, identifies potential problems, and proposes fixes to incorporate back into the spec.

When do I need an independent spec review in the software development lifecycle?

The best way to validate requirements is using an independent second-model Codex review, which distinguishes itself by assuming no requirements are settled and proactively surfacing contradictions rather than just confirming the existing spec.

What limitations should I expect when reviewing a specification with a different model?

Run codex-spec-review on your finalized spec or PRD. The skill performs an independent review using a different Codex model to identify ambiguities, missing criteria, and contradictions, then proposes fixes to fold back into the document.