What problem does it solve?
Prompts for commands, hooks, skills, and subagent instructions are often deployed untested, so nobody knows whether they actually change agent behavior or which failures they need to fix. This Skill applies test-driven development to prompt engineering so every prompt is validated against real agent behavior before release.
Core Features & Use Cases
- Baseline (RED) Testing: Run scenarios without the prompt using isolated subagents to document exactly how agents fail, including verbatim rationalizations.
- Prompt Authoring (GREEN): Write minimal prompts that address only the documented baseline failures, with guidance per prompt type (instruction, discipline-enforcing, guidance, reference, subagent).
- Optimization (REFACTOR): Close loopholes, improve clarity via meta-testing, and reduce token usage while re-verifying behavior with fresh subagents.
- Use Case: Before shipping a new
/git:commit command, run baseline scenarios to watch an agent commit broken files under time pressure, write the command to counter those failures, then stress-test it until it resists rationalization.
Quick Start
Ask the agent to test your new prompt with the test-prompt skill by running baseline scenarios in subagents before finalizing it.