CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/decision-table-test-design

Derives human-readable manual test cases from a business-rule spec via a decision table: identify conditions and actions, build the full 2^n-column matrix, collapse columns with irrelevant entries, strike infeasible combinations, then emit one test case per remaining column (each feasible column is one coverage item per ISTQB CTFL v4.0 section 4.2.3). A deep single-technique walkthrough rather than a broad multi-lens case matrix; the output is manual step/expected cases rather than parameterized test code, and it covers how cases are derived rather than how a case record is structured. Use when a spec's outcome depends on interacting conditions (pricing, eligibility, discounts, routing rules) rather than the boundaries of a single input.

93

1.02x
Quality

93%

Does it follow best practices?

Impact

94%

1.02x

Average score across 10 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured procedural skill with a concrete worked example, explicit validation checkpoints, and a properly split one-level reference. Minor trimming of repeated syllabus quotes would tighten it further.

Suggestions

Consolidate the repeated §4.2.3 inline quotes into a single citation in the References section and paraphrase the procedure steps to reduce token overhead.

Move the full 8-column intermediate table (Step 2) or the syllabus-notation definitions into the reference file, keeping only the collapsed final table in the body.

DimensionReasoningScore

Conciseness

Largely lean and procedural with a carried worked example, but repeated inline quoting of the §4.2.3 syllabus at each step adds padding that could be trimmed without losing the procedure.

4 / 5

Actionability

Fully actionable for an instruction-only skill: exact notation (T/F/-/N/A, X), mechanically filled tables per step, and a copy-paste-ready test-case table with TC IDs, setup, action, and expected result.

5 / 5

Workflow Clarity

Steps 1–5 are explicitly sequenced with an embedded validation/feedback loop — Step 2 flags columns with '?', Step 4 resolves feasibility, and a constraint check with 'if that check fails, the table must be rebuilt' provides error recovery.

5 / 5

Progressive Disclosure

Body holds the core procedure and signals a single one-level-deep reference for advanced material — 'Extended-entry tables and anti-patterns ... are in references/decision-table-details.md' — and that referenced file exists, keeping navigation shallow and clear.

5 / 5

Total

19

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that names concrete actions and explicit trigger conditions while clearly distinguishing the skill from neighboring techniques. Voice is third-person throughout with no first/second-person drift.

DimensionReasoningScore

Specificity

Lists multiple concrete actions in sequence — 'identify conditions and actions, build the full 2^n-column matrix, collapse columns with irrelevant entries, strike infeasible combinations, then emit one test case per remaining column' — giving comprehensive coverage of the technique.

5 / 5

Completeness

Explicitly answers both: what ('Derives human-readable manual test cases from a business-rule spec via a decision table: ...') and when ('Use when a spec's outcome depends on interacting conditions ... rather than the boundaries of a single input').

5 / 5

Trigger Term Quality

Includes natural domain phrases a user would say — 'business-rule spec', 'interacting conditions', and concrete triggers '(pricing, eligibility, discounts, routing rules)' — though a few common synonyms (e.g. 'business rules', 'combinatorial testing') are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche and explicitly differentiates from siblings — 'A deep single-technique walkthrough rather than a broad multi-lens case matrix' and 'rather than the boundaries of a single input' — minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Reviewed

Table of Contents