State transition
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 state-transitionAssembled 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 a system has discrete states, events, guards, or lifecycle phases and Codex needs transition-focused test design.
SKILL.md
1.8 KB, as published. Nobody here has run it
State Transition
Read First
./references/state-transition.md./references/test-design-shared-conventions.md./assets/templates/state-table.j2./assets/templates/state-transition-table.j2./assets/templates/test-case-list.j2
Workflow
- Identify states, events, guards, and resulting actions.
- Confirm the start state and invalid-transition behavior when the requirement does not make them obvious.
- Build a transition model before writing tests.
- Select the coverage target: all states, all transitions, or switch coverage.
- Include invalid-transition tests when the system rejects illegal events explicitly.
Required Output
- state inventory
- transition model
- path set for the requested coverage level
- negative-transition scenarios when supported
- traceable test list
Guardrails
- Do not use state-transition testing when the requirement is really just a rule matrix or a simple range check.
- Do not invent hidden states to make the model look complete.
- Separate valid transitions from inferred invalid ones.