test-cases

Generates structured test case documentation with steps, test data, and requirement traceability.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill test-cases-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-cases
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/quality/test-cases
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill test-cases-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing test cases by hand is slow and inconsistent, and cases often lose their link back to requirements. This Skill generates a complete, standardized test cases document from an approved test plan and functional specification, with every case traced to a requirement ID. ## Core Features & Use Cases - Structured Test Case Catalog: Produces per-module test cases with IDs, priorities, preconditions, numbered steps, and expected results following a fixed naming convention. - Mandatory E2E Journey Coverage: Generates one end-to-end test case per user journey from the experience design document, including navigation assertions and failure recovery. - Traceability and Coverage Matrices: Builds a requirement-to-test-case traceability matrix and per-module coverage summary so gaps are visible before sign-off. - Use Case: After your test plan is approved, run this Skill to produce a signed, QA-Lead-approved test cases document covering functional, negative, boundary, and end-to-end scenarios for every module. ## Quick Start Ask the agent to generate the test cases document for your project based on the signed test plan and functional specification.

Frequently Asked Questions about test-cases

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate test cases from a functional specification?▼

Provide the signed test plan and functional specification, then invoke the test-cases skill. It derives one section per module from the functional requirements and emits test cases with steps, expected results, and traceability to requirement IDs.

What should a test case document include?▼

A test case document should include a summary index, per-module cases with preconditions and numbered steps, test data requirements, a requirement traceability matrix, and coverage by module. This Skill generates all of these sections.

Does this skill cover end-to-end testing scenarios?▼

Yes, it mandates one TC-E2E case per user journey defined in the experience design document. Each E2E case includes screen traversal steps, navigation assertions, and failure recovery instructions.

What prerequisites are needed before writing test cases?▼

The test plan and functional specification documents must exist and be signed before this skill runs. The skill blocks execution and reports which prerequisite is missing if validation fails.

How is requirement traceability enforced in test cases?▼

Every test case must reference a requirement ID such as FR-XXX or NFR-XXX, and a traceability matrix maps each requirement to its covering cases. Cases without a traceable requirement must be resolved before sign-off.