CtrlK
BlogDocsLog inGet started
Tessl Logo

testland/test-case-ideation-from-story

Takes a user story or feature spec and emits a markdown test-case matrix - one row per case (id, title, precondition, steps, expected, tier) covering happy path, alternate paths, boundaries, and negative paths - before any test code is written. Output is the human-reviewable matrix that goes into TestRail / Qase / Xray. Emits the human-reviewable case matrix itself - not Gherkin scenarios written against locked acceptance criteria, and not executable test code. Use as the first artifact a manual tester or three-amigos session produces from a story, ahead of automation.

73

Quality

92%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

Quality

Content

88%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.

The body is dense, actionable, and workflow-driven with a genuine validation checkpoint, assuming domain competence rather than explaining basics. Progressive disclosure is solid given there are no bundle files, with references cleanly separated.

DimensionReasoningScore

Conciseness

Information-dense and assumes QA/ISTQB competence (equivalence partitioning, boundary value analysis, decision tables are named, not explained), with references cleanly in a footer; a couple of narration passages (e.g. the PractiTest statistic framing) could be trimmed.

4 / 5

Actionability

Highly concrete: an explicit six-field extraction checklist, a parameter-to-equivalence-class table, an exact boundary recipe (min, min-1, max, max+1), defined required matrix columns, and a full five-row worked example with stable IDs.

5 / 5

Workflow Clarity

Clear four-step sequence (Extract → Enumerate → Emit → Integrate) with an explicit validation checkpoint in Step 1 that halts and requests clarification when actor/postconditions are missing, plus an anti-patterns table reinforcing correct execution.

5 / 5

Progressive Disclosure

Well-organized into clearly signaled sections with one-level-deep external references gathered in a References footer and cited inline; no bundle files exist, so references are URLs rather than a structured file tree, a minor organization gap.

4 / 5

Total

18

/

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.

The description is specific, trigger-rich, and complete, clearly bounding what the skill produces and when to reach for it while drawing a hard line against adjacent BDD/automation skills. The only minor gap is missing a few common synonyms a user might naturally say.

Suggestions

Consider adding common synonyms a user might actually say (e.g. "test plan", "test scenarios", "break down a story for QA") so the trigger matches more natural phrasings.

The opening clause describing what a thin story looks like is long; tightening it would reduce verbosity without losing the trigger signal.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with a defined output shape: "emits a markdown test-case matrix, one row per case (id, title, precondition, steps, expected, tier)" covering happy path, alternate paths, boundaries, and negative paths.

5 / 5

Completeness

Clearly answers both what (markdown test-case matrix with named columns across four path types) and when ("Use when a story needs its cases enumerated and agreed before automation starts") with concrete triggers.

5 / 5

Trigger Term Quality

Strong natural QA vocabulary (story, feature spec, test-case matrix, happy path, boundaries, negative paths, TestRail / Qase / Xray, "cases enumerated before automation"), but a few common synonyms a user might say (test plan, test scenarios) are absent even though Gherkin is explicitly disambiguated.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (human-reviewable matrix authoring from stories), explicitly contrasted against Gherkin scenarios and downstream automation, minimizing wrong-skill triggers.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Reviewed

Table of Contents