Test Designer

Independent test-design orchestrator. Encodes Independent Evaluation: the agent writing the tests must not be the agent implementing the feature, and must not inherit the implementation's assumptions.

When to Use

• TDD red phase for a complex / non-trivial feature (multi-file, multi-branch logic, new subsystem)
• Requirement is ambiguous enough that the implementer's tests would likely rationalize the implementation instead of catching bugs
• User explicitly asks for "independent test design", "fresh-eyes tests", or runs /test-designer

Don't use for:

• Trivial changes (one-line fix, rename) — just write the test inline
• Bug reproduction tests — write directly from the bug report
• Non-code changes (pure docs, pure config, pure prompt)

The Iron Law

The agent designing the tests must not carry the implementation's context. If you (the main Agent) are about to implement the feature, you are disqualified from designing its tests. Dispatch.