TestDefinitionAgent

Name: TestDefinitionAgent
Availability: InStock
Author: farmountain

Define verifiable test cases and evidence requirements for software components.

1|Updated Jan 29, 2026

Search Tags:#testing #tdd #quality assurance #verification #test definition #evidence gating

Ready to run

npx skills add https://github.com/farmountain/sdlc_agent_swarm --skill testdefinitionagent

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: TestDefinitionAgent
Source: https://github.com/farmountain/sdlc_agent_swarm/tree/main/vscode-sdlc-swarm/templates/.agents/skills/test-agent
Command: npx skills add https://github.com/farmountain/sdlc_agent_swarm --skill testdefinitionagent

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill ensures that tests are defined as explicit requirements before any code execution begins, acting as a crucial gate for verifiable evidence.

Core Features & Use Cases

Test Definition: Creates structured TEST Cards outlining objectives, evidence, and verification methods.
Evidence Gating: Prevents execution plans until test definitions are complete.
Use Case: When developing a new feature, use this Skill to first define what constitutes a successful test and what evidence will prove it, ensuring quality from the outset.

Quick Start

Use the TestDefinitionAgent skill to define tests for the new user authentication module.

Frequently Asked Questions about TestDefinitionAgent

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

FAQPage Schema

How do I define verifiable test cases for software components before execution?▼

To define verifiable test cases for software components, generate structured TEST Cards specifying objectives, required artifacts, verification procedures, and negative test scenarios prior to code execution. This evidence gating ensures tests align with quality gates and TDD methodologies.

What is evidence gating in test definition and quality assurance?▼

Evidence gating in test definition is a mechanism that prevents execution plans from proceeding until structured test definitions and their required evidence are complete. It acts as a quality assurance gate to guarantee verifiable proof exists before software execution begins.

How do I structure test objectives and verification procedures for TDD?▼

You structure test objectives and verification procedures for TDD by creating TEST Cards that explicitly outline what constitutes a successful test, the required artifacts, and the verification methods needed. This ensures quality from the outset of feature development.

Can I block execution plans until test definitions are complete?▼

Yes, you can block execution plans until test definitions are complete by applying evidence gating. This feature ensures that no execution plan proceeds unless structured TEST Cards specifying objectives, artifacts, and verification procedures are fully defined.

What are negative test scenarios and how do I specify them in test definition?▼

Negative test scenarios are failure cases defined within structured TEST Cards to verify how software components handle invalid inputs or errors. You specify them during test definition to ensure comprehensive verification procedures and evidence requirements cover edge cases.

When do I need to define test cases as explicit requirements before coding?▼

You need to define test cases as explicit requirements before coding when adopting TDD methodologies or requiring strict quality assurance. Defining tests first acts as a crucial gate for verifiable evidence, ensuring all execution plans meet predefined quality gates.