codex-external-reviewer

Invoke the Codex CLI to review sprint artefacts and produce a YAML verdict.

Updated May 5, 2026
One-click install
npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill codex-external-reviewer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: codex-external-reviewer
Source: https://github.com/shakhovskiya-create/shakhoff-claude-marketplace/tree/main/plugins/ai-scrum/skills/codex-external-reviewer
Command: npx skills add https://github.com/shakhovskiya-create/shakhoff-claude-marketplace --skill codex-external-reviewer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides an independent second opinion on sprint changes by leveraging the Codex CLI when Codex is installed, ensuring a structured verdict when Codex is available and gracefully falling back when it's not.

Core Features & Use Cases

  • External Codex review for cross-model verification during sprint cycles.
  • Graceful fallback when Codex is unavailable or blocked, with observability hooks.
  • Enforces standardized review outputs with metadata for sprint metrics and traceability.

Quick Start

Run an external Codex review for the current sprint and save the verdict to the codex-review file under .sprints/active/reviews.

Frequently Asked Questions about codex-external-reviewer

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

FAQPage Schema
How do I get a second opinion on sprint readiness using Codex?

To get a second opinion on sprint readiness using Codex, you can invoke an external review process against your current sprint artefacts to generate a structured verdict with duration and provenance for auditing.

What happens to my external code review if the Codex CLI is unavailable?

If the Codex CLI is unavailable or blocked, the external code review process will execute a graceful fallback, ensuring observability hooks are maintained and documenting the fallback state within the review file.

How do I format sprint review outputs for metrics and traceability?

You format sprint review outputs for metrics and traceability by enforcing a standardized YAML frontmatter in the review file, capturing the final verdict, duration, and provenance under the active sprint reviews directory.

When do I need an external review for cross-model verification during sprint cycles?

You need an external review for cross-model verification during sprint cycles when you require an independent, external assessment of your sprint changes to validate readiness before finalizing the sprint.

Does the Codex external review process require any specific dependencies?

The Codex external review process does not require specific dependencies to function, as it is designed to provide a structured verdict when Codex is installed and a graceful fallback when it is not.