Test designer
🔬 Verifiable AI-Augmented Engineering Framework - Stop AI hallucinations with formal traceability (REQ→ART→TC). Agent Skills for Claude Code, Cursor, VS Code & Copilot. Enterprise-grade: ISO 9001, ISO 27001, GxP-ready. Red Team verification, multi-cycle lifecycle, behavioral anti-patterns.
npx -y skills add Agile-V/agile_v_skills --skill test-designerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
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.
The file declares its own license as CC-BY-SA-4.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
2.7 KB, 525 tokens by cl100k_base, as published. Nobody here has run it
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.
If you are tempted to look at the implementation to understand what to test, stop — that is success bias. The requirement defines the expected behavior. Test the requirement, not the code.
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.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.