# test_driven_qa

test_driven_qa — a subagent for Claude Code turns requirements and repository materials into a QA plan or test artifact. It ranks test scenarios and keeps observed evidence separate from proposed checks.

- subagent · `type=agent` · Claude Code, Codex, Cursor · ★ 776 repo stars
- Author: AgenticOrgLab
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/test_driven_qa.md
- Updated: 2026-11-12
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/agents/test-driven-qa

## What it does

The subagent examines acceptance criteria, relevant code, existing tests, configuration, and dependency details, then writes a Markdown QA report. The report covers risks, ranked scenarios, needed fixtures and mocks, environment assumptions, coverage gaps, and explicit pass/fail criteria. It can also give reproduction steps for a supplied failure.

Where relevant, its scenarios cover boundary conditions and failures, including empty or oversized input, timeouts, and upstream errors. The report depends on the requirements and repository context provided; it does not claim tests ran without execution evidence. Its response contains the requested artifact, with no greeting or hidden reasoning.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/agents/test_driven_qa.md` — For all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention

### Codex

**Manually: put the files in place**
- File: `.codex/agents/test_driven_qa.toml` — Codex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/

### Cursor

**Manually: put the files in place**
- File: `.cursor/agents/test_driven_qa.md` — Cursor also reads .claude/agents/

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/AgenticOrgLab/ExecOrchestra/tree/HEAD/execorchestra/Pool/resources/agents/test_driven_qa.md

## When to use it
- draft a ranked test plan for a feature change
- identify boundary and failure cases from acceptance criteria
- define coverage gaps and pass/fail criteria
- write reproduction steps for a reported failure

## Example prompts
- Create a QA plan from these acceptance criteria and the repository code.
- Review this test output and write steps to reproduce the failure.
- List boundary cases and the fixtures or mocks needed to test them.

## Similar
- [test-planning](https://affpapa.org/en/nevibecode/skills/test-planning.md) — skill · 1900 installs
- [qa-start](https://affpapa.org/en/nevibecode/skills/qa-start.md) — skill · 1400 installs
- [QA](https://affpapa.org/en/nevibecode/agents/github-qa.md) — subagent · ★ 41430 repo stars
- [test-driven-development](https://affpapa.org/en/nevibecode/skills/test-driven-development.md) — skill · 259292 installs
- [convert-to-test-driven-prompt](https://affpapa.org/en/nevibecode/commands/convert-to-test-driven-prompt.md) — command · ★ 2744 repo stars
- [go-test-table-driven](https://affpapa.org/en/nevibecode/skills/go-test-table-driven.md) — skill · ★ 90 repo stars

From the same set: [agenticorglab/execorchestra](https://affpapa.org/en/nevibecode/by/agenticorglab/execorchestra.md) — 24 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
