skills.rest
foolishimp
foolishimpCOMMUNITY
Explore all skills by this author →
GitHub

create-test-specification

Generate Test Case Specification documents with requirement traceability to ADRs and tests.

Updated Aug 27, 2026
Search Tags:#requirements#traceability#tests#TCS#test-specification
One-click install
npx skills add https://github.com/foolishimp/ai_sdlc_method --skill create-test-specification
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-test-specification
Source: https://github.com/foolishimp/ai_sdlc_method/tree/main/claude-code/.claude-plugin/plugins/aisdlc-methodology/skills/testing/create-test-specification
Command: npx skills add https://github.com/foolishimp/ai_sdlc_method --skill create-test-specification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill creates Test Case Specifications (TCS) that map requirements to test scenarios, ensuring traceability from requirements to tests within docs.

Core Features & Use Cases

  • TCS Document: Produces a structured TCS file with requirement traceability.
  • Scenarios & Validation: Includes test scenarios, validation criteria, and implementation references.
  • Traceability: Links TCS to REQ-* and ADRs.

Quick Start

Create TCS-010 for REQ-F-CART-001 with two test scenarios and traceability to ADR/REQ.

Frequently Asked Questions about create-test-specification

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

FAQPage Schema
How do I create a Test Case Specification document with requirement traceability?▼

A Test Case Specification (TCS) document maps requirements to test scenarios with full traceability. This Skill generates structured TCS files that link requirements (REQ-*), architectural decisions (ADRs), implementation paths, test scenarios, and validation criteria in a single document during system testing.

What should a TCS document include to ensure requirements coverage?▼

TCS documents must include status, date, requirement references, ADR links, implementation paths, test purpose, preconditions, test scenarios, validation criteria, and traceability to design artifacts. This Skill produces complete TCS files with all these elements structured for validation of requirement coverage.

When do I need to generate a Test Case Specification for a component?▼

Generate TCS documents during the System Test stage for new components and functionality. TCS enables validation that all functional and technical requirements are covered by test scenarios and linked to their corresponding ADRs and implementations.

Can I link test scenarios directly to requirements and architecture decisions in a TCS?▼

Yes. This Skill generates TCS documents with explicit traceability: each test scenario links to specific requirements (REQ-*), references relevant ADRs, traces implementation paths, and validates against acceptance criteria, creating a complete audit trail.

What's the difference between a TCS and a simple test plan?▼

A TCS provides granular, requirement-level traceability with scenario detail and validation criteria tied to specific requirements and design decisions. Unlike general test plans, TCS documents ensure every requirement has a mapped test scenario with documented preconditions and acceptance validation.

Related Skills

Explore More Software Engineering Skills→
jabrenajabrena
423

030-architecture-adr-general

Generate Architecture Decision Records for Java projects through interactive conversation.

Community
Advanced
ref-docsref-docs

traceability-auditor

Validate end-to-end traceability across requirements, design, tasks, code, and tests.

Official
Advanced
jralphjralph

task-planner

Create implementation tasks with requirements and design traceability.

Community
Basic
pradyumnasagarpradyumnasagar
6

roadmap-author

Guide authors through creating and validating ORS SKILL.md files.

Community
Intermediate