test-design-orchestrator

Turn requirements, user stories, acceptance criteria, business rules, use cases, or state models into structured test artifacts. Selects the best black-box test design technique and routes work to the matching subskill. For format-only work, prefer test-artifact-export-skill.

Use this skill when Codex needs to convert user stories or acceptance criteria into traceable behavior-focused scenarios or structured test cases.

Use this skill when a requirement contains ordered values such as ranges, lengths, dates, counts, or sequence limits and Codex needs boundary-focused test scenarios.

Use this skill when Codex needs to model interacting parameters and generate reduced pairwise or n-wise combinations instead of an impractical full Cartesian set.

Use this skill when requirements describe discrete business rules, multiple conditions, or outcome logic that should be modeled as a rule table.

Use this skill when Codex needs to derive representative tests from input classes that should behave the same within each valid or invalid partition.

Use this skill when a system has discrete states, events, guards, or lifecycle phases and Codex needs transition-focused test design.

Use this skill when Codex needs to choose the best black-box test design technique for a requirement, user story, rule set, workflow, or state model before generating tests.

Compatibility bridge for the old test-design-orchestrator formatter entrypoint. Prefer the standalone `test-artifact-export-skill` skill for formatting existing test cases, BDD/TDD/plain-text rendering, and tool-export artifacts.

Use this skill when requirements are expressed as actor-system interactions with preconditions, main flows, alternate flows, and postconditions.