Technique selector
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 technique-selectorAssembled 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 choose the best black-box test design technique for a requirement, user story, rule set, workflow, or state model before generating tests.
SKILL.md
2.1 KB, as published. Nobody here has run it
Technique Selector
Select the best-fit technique. Do not generate the final test cases here.
Read First
./references/technique-selection-matrix.md./references/test-design-shared-conventions.md
Decision Process
- Identify the dominant problem shape:
- ordered ranges or limits
- equivalence classes
- discrete rules and outcomes
- interacting parameters
- states and transitions
- actor-system flows
- acceptance criteria at behavior level
- Check whether the user already mandated a technique.
- If the scenario is too vague to distinguish between two plausible techniques, ask a focused clarification question instead of guessing.
- Prefer the technique that best matches the main defect risk, not the technique that produces the largest number of tests.
Required Output
Return a compact recommendation with exactly these sections:
Primary techniqueWhy it fitsSecondary optionWhy not the othersMissing information, only if the analysis is blocked or materially uncertain
Guardrails
- Recommend one primary technique.
- Name a secondary option only when it is genuinely plausible.
- If the artifact mixes several shapes, choose the one that should drive the first pass and mention any residual gap briefly.
- Do not produce tables, test steps, or detailed scenarios in this skill.