s-requirements-review-codex

Review requirements documents and GitHub issues against repository code.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/gyarra/cine_medallo_2 --skill s-requirements-review-codex
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: s-requirements-review-codex
Source: https://github.com/gyarra/cine_medallo_2/tree/main/.claude/skills/s-requirements-review-codex
Command: npx skills add https://github.com/gyarra/cine_medallo_2 --skill s-requirements-review-codex

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Codex is used to review requirements documents or GitHub issues before implementation to surface ambiguities, gaps, and potential risks, reducing rework and misinterpretation.

Core Features & Use Cases

  • Codex-based requirements review: Have Codex evaluate the provided requirements text or issue to challenge assumptions and validate completeness.
  • Flexible input sources: Accepts GitHub issues, plan files, or inline text, ensuring feedback is grounded in the actual work item.
  • Structured feedback workflow: Produce a prioritized set of findings, questions, and recommendations to inform planning and scoping.
  • Use Case: Before starting a large feature, run Codex review to catch edge cases and clarify acceptance criteria.

Quick Start

Provide Codex with the full requirements text and run a read-only review to surface potential issues and recommended next steps.

Frequently Asked Questions about s-requirements-review-codex

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

FAQPage Schema
How do I review a GitHub issue for edge cases and data model fit before coding?

To review a GitHub issue, you can load the exact issue text and repository context into Codex to run a read-only evaluation. This process identifies correctness issues, data model fit, edge cases, and migration implications, returning a prioritized summary of findings and actionable follow-ups.

What is the best way to stress-test requirements documents against an existing codebase?

Stress-testing requirements against a codebase involves running a read-only review using Codex to ground feedback in actual files. Codex evaluates the provided requirements text or plan files to challenge assumptions, surface ambiguities, and validate completeness before implementation begins.

Can I use Codex to check migration implications in a requirements document?

Yes, Codex can check migration implications by operating in a read-only mode against your repository. It loads the full requirements text and context to specifically identify migration risks, correctness issues, and data model fit as part of a structured feedback workflow.

How do I get structured feedback on a plan file before starting a large feature?

Getting structured feedback on a plan file requires providing Codex with the full text and running a read-only review. Codex challenges assumptions and validates completeness, producing a prioritized set of findings, questions, and recommendations to inform planning and scoping.

Does Codex requirements review modify the repository during analysis?

Codex requirements review operates strictly in read-only mode against the repository and does not modify files. It loads text and context to ground its feedback, ensuring the analysis only surfaces potential issues and recommended next steps without altering the codebase.

What input sources are supported for running an AI-assisted requirements review?

AI-assisted requirements review supports flexible input sources including GitHub issues, plan files, and inline text. This ensures that Codex feedback is grounded in the actual work item, allowing it to effectively challenge assumptions and validate completeness regardless of input format.