codex-plan-review

Review implementation plan documents for gaps, risks, and convention drift.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

šŸ’” This Skill includes scripts (resource) components.

What problem does it solve?

Provides an independent review of implementation plans before any code is written, catching gaps, ordering issues, and potential risks.

Core Features & Use Cases

  • Independent Review: Gets a review from an external Codex model for a unbiased perspective.
  • Review Plan Documents: Inspects plan files for gaps, missing tests, risks, and more.
  • Proposed Fixes: Offers concrete fixes to address identified issues.
  • Use Case: Before writing code, get a review to ensure the implementation plan is comprehensive and well-structured.

Quick Start

Get a second-opinion review of your plan with codex-plan-review.

Frequently Asked Questions about codex-plan-review

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

FAQPage Schema
How do I review an implementation plan for missing steps and risks before coding?ā–¼

Review an implementation plan by providing a plan document path to get a severity-sorted list of missing steps, unsafe ordering, test coverage gaps, and unstated assumptions with concrete fixes.

What is a second-opinion plan review and how does it work?ā–¼

A second-opinion plan review is an independent assessment of a plan document that identifies drift from project conventions and large steps, providing a final review verdict to ensure comprehensive planning.

Can I use a markdown file for automated risk assessment of my implementation plan?ā–¼

Yes, you can pass a markdown file path for risk assessment, or the system can automatically detect the most recent .md file in your directory to evaluate test coverage gaps and ordering issues.

What is the best way to catch project convention drift in implementation planning?ā–¼

The best way to catch project convention drift is to run an independent review on your plan document, which flags unstated assumptions and deviations while offering concrete fixes before code is written.

Do I need a specific plan document format to check for test coverage gaps?ā–¼

You need a markdown plan document to check for test coverage gaps, as the review operates on plan files to detect large steps and unsafe ordering while returning a severity-sorted issue list.