One-click install
npx skills add https://github.com/juanca202/sdd-devkit --skill test-define-juanca202
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-define
Source: https://github.com/juanca202/sdd-devkit/tree/main/skills/test-define
Command: npx skills add https://github.com/juanca202/sdd-devkit --skill test-define-juanca202

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Turning acceptance criteria from user stories, work items, or any specification document into consistent, traceable test case documentation is slow and error-prone. This Skill automates that conversion, producing one TC-XXX markdown file per scenario with full traceability back to each criterion. ## Core Features & Use Cases - Criteria-driven test generation: Reads acceptance criteria with coded identifiers (AC-001, 1.1, R-3, etc.) from US-XXX, WI-XXX, FT-XXX artifacts or any external specification document, and generates test cases covering happy path, error, and boundary perspectives. - Standardized IEEE 29119-4 structure: Each test case follows a template with preconditions, test data, execution steps, expected results, priority, and test type (Manual, Unit, Integration, API Test, Visual Test, E2E), plus an auto-maintained index README. - Azure DevOps integration: When a project management integration is active, creates Test Case work items inside the correct Test Plan and Test Suite hierarchy via MCP, using the ADO id as the TC number. - Use Case: After writing a user story with acceptance criteria AC-001 through AC-005, ask the agent to define test cases; it interviews you about environment and test data, then produces traceable TC files under the story's test-cases/ folder. ## Quick Start Ask the agent to define test cases for US-003 following the test-define skill, covering all acceptance criteria.

Frequently Asked Questions about test-define

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

FAQPage Schema
How do I generate test cases from acceptance criteria?▼

Invoke the skill with a reference to your artifact (US-XXX, WI-XXX, FT-XXX, or a document path). It reads the acceptance criteria, optionally interviews you about environment and test data, then writes one TC-XXX markdown file per scenario plus an index.

What format do the generated test cases follow?▼

Test cases follow the IEEE 29119-4 structure: title in Given-When-Then format, perspective (Happy Path, Error, Limit), test type, priority, preconditions, test data table, execution steps, and final expected result. Each criterion gets coverage from up to three perspectives.

Does it work with specification documents outside the plugin?▼

Yes. Any specification document works as long as its acceptance criteria have unique coded identifiers; the format is irrelevant (AC-001, 1.1, R-3 all valid). Test cases are saved in a test-cases/ folder next to the source document.

Can test cases be synced to Azure DevOps?▼

Yes. When the project management integration is active with the azure-devops provider, the skill creates Test Case work items via MCP inside a Test Plan and Test Suite hierarchy, and uses the ADO work item id as the TC number.

Why does test generation stop with a traceability error?▼

Generation stops when one or more acceptance criteria lack a unique coded identifier, since traceability requires literal references. Add identifiers to the criteria in the source artifact and restart; the skill never assigns identifiers automatically.

Does this skill write or execute test code?▼

No. It produces test documentation only: TC-XXX markdown files and an index README. It does not implement test code or run tests; automation of Ready test cases is handled downstream by the work-implement skill.