Decision table
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 decision-tableAssembled 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 requirements describe discrete business rules, multiple conditions, or outcome logic that should be modeled as a rule table.
SKILL.md
1.7 KB, as published. Nobody here has run it
Decision Table
Read First
./references/decision-table.md./references/test-design-shared-conventions.md./assets/templates/decision-table.j2./assets/templates/optimized-decision-table.j2./assets/templates/test-case-table.j2
Workflow
- Extract conditions and resulting actions.
- Distinguish stated rules from unstated combinations.
- Build the full rule space only as far as the requirement supports it.
- Mark impossible or unspecified combinations explicitly.
- Optimize only when multiple columns truly produce the same outcome and the same oracle.
- Derive one scenario per retained rule column.
Required Output
- condition list
- action list
- full or partially constrained decision table
- optimized decision table when valid
- scenario list tied back to retained rules
Guardrails
- Do not invent policy for unspecified combinations.
- Do not use "don't care" to hide a meaningful rule difference.
- Prefer a coverage gap note over a fake complete matrix.