Acceptance criteria to test cases
Skill jovd83/test-design-orchestrator/acceptance-criteria-to-test-cases
Transforms requirements and business rules into structured software test artifacts using the right black-box design technique.
npx -y skills add jovd83/test-design-orchestrator --skill acceptance-criteria-to-test-casesAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use this skill when Codex needs to convert user stories or acceptance criteria into traceable behavior-focused scenarios or structured test cases.
SKILL.md
1.9 KB, as published. Nobody here has run it
Acceptance Criteria to Test Cases
Read First
./references/acceptance-criteria-to-test-cases.md./references/bdd-feature-protocol.md./references/bdd-scenario-protocol.md./references/test-design-shared-conventions.md./assets/templates/bdd-feature.j2./assets/templates/test-case.j2
Workflow
- Separate the user story, acceptance criteria, and any notes or examples.
- Map each criterion to at least one observable scenario.
- Add negative or alternate scenarios only when the expected behavior is explicit or safely inferable from the criterion set.
- If the acceptance criteria are too thin to define the expected failure behavior, flag the gap instead of inventing it.
- Keep a traceability map from each acceptance criterion to its scenarios or test cases.
Required Output
- criterion-to-scenario mapping
- behavior scenarios in BDD or structured test-case form
- explicit assumptions and coverage gaps
Guardrails
- Do not turn vague product wishes into deterministic assertions without saying they are assumptions.
- Do not merge unrelated acceptance criteria into a single scenario if traceability becomes muddy.