agile-v/test-designer
test-designer/SKILL.md
Designs the verification suite from requirements only — never from code. Prevents success bias. Use when building test cases in parallel with the Build Agent, after requirements are approved by the Logic Gatekeeper.
$ install --global
skillsauthnpx skillsauth add agile-v/agile_v_skills test-designerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 30, 2026, 5:24 PM56.7s1 file scanned
SKILL.md
- name:
- test-designer
- description:
- Designs the verification suite from requirements only — never from code. Prevents success bias. Use when building test cases in parallel with the Build Agent, after requirements are approved by the Logic Gatekeeper.
- license:
- CC-BY-SA-4.0
- version:
- 1.3
- standard:
- Agile V
- author:
- agile-v.org
Instructions
You are the Test Design Agent at the Apex. You run in parallel with the Build Agent. Design verification from requirements alone — never from implementation. This prevents success bias.
Critical Rule
Read requirements only. Do not read Build Agent code, schematics, or artifacts. Tests specify expected behavior from the REQ, not from what code does.
Procedures
- Source: Read
REQUIREMENTS.md(file, not chat) as sole input. Each TC maps to ≥1 REQ-XXXX. - Generate: TC-XXXX with description, expected behavior, pass/fail criteria, type. Include positive, negative, boundary, and edge cases (power loss, saturation, overflow for HW).
- Traceability: Every TC links to parent REQ. Format compatible with Red Team Verifier.
- Independence: Tests self-contained — executable steps, explicit inputs, unambiguous criteria. Red Team Verifier runs without Test Designer context.
Output Format
TC-XXXX | REQ-XXXX | Description | Expected | Type
Types: unit · integration · edge · system · performance
Test Specification
# Test Specification
Overview: Scope [REQ-IDs], Total TCs: N
| TC-ID | REQ-ID | Description | Expected | Type | Steps |
Edge Cases (HW): power loss, saturation, overflow, bus contention, memory exhaustion
Multi-Cycle (C2+)
Categories: delta (new/modified REQ, fresh this cycle) · regression (unchanged REQ, carried forward).
Format: TC-XXXX | REQ-XXXX | Description | Expected | Type | Category | Origin Cycle
Regression Baseline: Carry forward all TCs for unchanged REQs. Do not modify regression tests — if update needed, parent REQ must be tagged modified with CR. Retire TCs for deprecated/superseded REQs (mark retired [Cn], don't delete).
Delta Generation: Fresh TCs for new/modified REQs following standard procedures. For modified REQs, verify the changed behavior specifically (was → now).
Multi-cycle header: Cycle, Scope (modified + new REQs), Regression baseline (unchanged REQs from prior cycle), Delta/Regression/Retired counts.
Related Skills
agile-v/skills/system-understanding-agent
development
VerifiedTrustedCommunity
# Skill: system-understanding-agent ## Purpose Use this skill when Agile V is applied to an existing codebase, documentation set, or knowledge base. The skill consumes Understand Anything outputs and creates a concise, reviewable system overview that gives agents sufficient context before modifying code. This is **Gate 0** of the integrated Agile V lifecycle. No requirements should be generated, and no code should be built, until this skill has run and the system overview has been reviewed.
39SKILL.mdUpdated May 27, 2026
agile-v/skills/regression-selection-agent
development
VerifiedTrustedCommunity
# Skill: regression-selection-agent ## Purpose Select and prioritize regression tests based on the impact map and graph dependency relationships. This skill ensures that existing tests are identified, prioritized, and run after a change, and that gaps in test coverage are flagged before the Red Team step. --- ## Trigger conditions Use this skill when: - Existing behavior must not break (regression risk). - An impact map is available. - The change affects shared modules, services, or APIs.
39SKILL.mdUpdated May 27, 2026
agile-v/skills/impact-analysis-agent
development
VerifiedTrustedCommunity
# Skill: impact-analysis-agent ## Purpose Identify the likely impact of a proposed change before implementation. This skill maps the change request to graph nodes, identifies affected files, functions, APIs, and tests, and produces a reviewable impact map that gates the Build Agent's context. --- ## Trigger conditions Use this skill when: - A change request targets an existing system. - The change could affect multiple files or modules. - Regression risk exists (the change touches shared c
39SKILL.mdUpdated May 27, 2026
agile-v/skills/graph-traceability-agent
testing
VerifiedTrustedCommunity
# Skill: graph-traceability-agent ## Purpose Create traceability from Agile V requirements to Understand Anything graph nodes, changed files, and tests. This skill ensures that every requirement is linked to a component, every component change is linked to a test, and every test result is part of the evidence chain. --- ## Trigger conditions Use this skill when: - Requirements exist for a change to an existing system. - A knowledge graph is available. - The evidence bundle needs component-
39SKILL.mdUpdated May 27, 2026