skills.rest
msd-dev-lab
msd-dev-labOFFICIAL
Explore all skills by this author →
GitHub

codex-review-requirements

Review requirements.md for completeness, feasibility, ambiguity, and EARS compliance.

Updated Jan 6, 2026
Search Tags:#documentation#requirements#codex#quality#review#EARS
One-click install
npx skills add https://github.com/msd-dev-lab/python-dev-template --skill codex-review-requirements
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: codex-review-requirements
Source: https://github.com/msd-dev-lab/python-dev-template/tree/main/skills/codex-review-requirements
Command: npx skills add https://github.com/msd-dev-lab/python-dev-template --skill codex-review-requirements

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides automated Codex reviews of requirements.md to ensure completeness, feasibility, ambiguity resolution, and proper EARS-style acceptance criteria, accelerating the path from requirements to design.

Core Features & Use Cases

  • Completeness checks: verifies coverage of functional and non-functional requirements, use cases, and edge cases.
  • Feasibility assessment: assesses technical viability against the project's tech stack and constraints.
  • Ambiguity detection: flags vague terms and proposes precise definitions.
  • EARS validation: ensures acceptance criteria use WHEN-IF-THEN structure and are testable.
  • Automated feedback loop: iterates until an ok: true state and then triggers deep-research prompt generation.

Quick Start

Run the review for a feature named 'auth-system': /codex-review-requirements auth-system The target file is at .kiro/specs/auth-system/requirements.md

Frequently Asked Questions about codex-review-requirements

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

FAQPage Schema
How do I validate EARS compliance in my requirements.md file?▼

EARS validation checks that acceptance criteria use WHEN-IF-THEN structure and are testable. The review targets .kiro/specs/{feature_name}/requirements.md, flagging non-compliant criteria and producing structured feedback with clarity scoring.

What is the best way to detect ambiguity in feature requirements?▼

Ambiguity detection scans requirements.md to flag vague terms and proposes precise definitions. The review assesses completeness, feasibility, and clarity, outputting structured feedback to resolve unclear language before design.

How do I review feature requirements for completeness and feasibility?▼

Reviewing requirements for completeness and feasibility verifies coverage of functional, non-functional, and edge cases against your tech stack constraints. The automated review scores the requirements.md file and iterates until passing.

Does the requirements review support iterative feedback loops?▼

Yes, the requirements review supports iterative feedback loops. It continuously assesses EARS compliance and completeness, running Codex review cycles until an ok: true state is achieved and triggering deep-research prompt generation.

Can I assess technical feasibility of requirements against my project's tech stack?▼

Yes, feasibility assessment evaluates technical viability against the project's tech stack and constraints. The review targets the requirements.md file, scoring feasibility and providing structured guidance to resolve identified issues.

What are the limitations of automated requirements quality reviews?▼

Automated requirements quality reviews require a valid file at .kiro/specs/{feature_name}/requirements.md. Without this exact path, the Codex review loop cannot execute completeness checks, ambiguity detection, or EARS validation.

Related Skills

Explore More Software Engineering Skills→
shimaMatzshimaMatz

kiro-spec-init

Initialize KiRo spec files from a project description and templates.

Community
Advanced
nnexainnexai
1

gsd-research-phase

Orchestrate specialized subagents to research implementation approaches and library options.

Community
Advanced
taku-otaku-o
1

kiro-spec-requirements

Generate EARS-format requirements drafts from project specs and steering files.

Community
Advanced
pczhao1210pczhao1210

azure-deployment-preflight

Validate Bicep templates and preview Azure deployment changes before execution.

Community
Advanced