Requirements to Acceptance Criteria Skill for Codex

Turn feature notes and draft specifications into observable acceptance criteria, test scenarios, dependencies, and open questions. The repository also includes a helper for checking Markdown specs for missing sections.

中文

Install in Codex

Use a Codex environment that can discover project skills. The example can be tested in a local project. The optional Markdown specification helper requires Python.

In a temporary directory, run git clone https://github.com/ClarentCinematics/Codex-Skills-for-Enterprise.git. Enter the clone, run git checkout --detach 3598e7788282b6548430aadfcbfcfd7181ebb02a, and review the pinned SKILL.md.
Copy the entire skills/requirements-to-acceptance-criteria folder to .agents/skills/requirements-to-acceptance-criteria in your own project, keeping its scripts, templates, and references together.
Open Codex in that project. Choose the skill with /skills or mention $requirements-to-acceptance-criteria, then run the example below. Restart Codex if the list does not refresh.

Example task

Provide this requirement: only administrators may export filtered orders, and an empty result should show a message. Ask for a normal case, an empty-result case, and a regular-user case, plus unanswered format questions.

What to check

Each scenario has a clear precondition, action, and observable outcome. Unspecified export columns, encoding, and order are flagged for confirmation.

Original SKILL.md on GitHub · Updated 2026-11-11

Frequently asked question

Can a one-line requirement produce complete acceptance criteria?

It can yield testable criteria for the behavior it states. Keep unspecified fields, error copy, and release conditions as questions for the product owner.