testing-skills-with-subagents

Run RED-GREEN-REFACTOR cycles to validate and harden skills against rationalization.

5|1|Updated Jan 26, 2026
One-click install
npx skills add https://github.com/ed3dai/ed3d-plugins-testing --skill testing-skills-with-subagents-ed3dai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-skills-with-subagents
Source: https://github.com/ed3dai/ed3d-plugins-testing/tree/main/plugins/ed3d-extending-claude/skills/testing-skills-with-subagents
Command: npx skills add https://github.com/ed3dai/ed3d-plugins-testing --skill testing-skills-with-subagents-ed3dai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, test-driven approach to validating and refining skills by executing RED-GREEN-REFACTOR cycles on process documentation, ensuring skills actually improve agent behavior under pressure.

Core Features & Use Cases

  • Red-Green-Refactor workflow: baseline testing without the skill, then iterative refinement with the skill.
  • Rationalization capture: logs exact failures and rationalizations to identify loopholes.
  • Meta-testing guidance: verifies the skill's effectiveness under challenging scenarios.

Quick Start

Run a baseline test campaign to observe agent failures without the skill, then implement and re-run against the same scenarios to confirm compliance.

Frequently Asked Questions about testing-skills-with-subagents

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stress-test agent documentation to prevent rationalization?

To stress-test agent documentation, you execute RED-GREEN-REFACTOR cycles that capture rationalizations and iteratively refine skills to close loopholes. This requires baseline scenarios to observe failures without the skill, then re-running against the same scenarios to confirm compliance.

What is the RED-GREEN-REFACTOR cycle for skill validation?

The RED-GREEN-REFACTOR cycle for skill validation is a test-driven approach where you run baseline tests without the skill, implement the skill to achieve compliance, and iteratively refactor the documentation to close loopholes. It ensures skills actually improve agent behavior under pressure.

How do I capture rationalizations when testing AI agents?

You capture rationalizations during testing by logging exact failures and agent justifications when the skill is challenged. This identifies specific loopholes in the documentation that need iterative refactoring to ensure the skill resists rationalization.

What is the best way to validate that skills improve agent behavior under pressure?

The best way to validate that skills improve agent behavior under pressure is by executing meta-testing guidance with baseline scenarios. You observe agent failures without the skill, then re-run against the same scenarios to confirm compliance and measure improvements.

Do I need baseline scenarios to run test-driven development on process documentation?

Yes, you need baseline scenarios to run test-driven development on process documentation. Baseline testing without the skill is required to observe initial agent failures and establish a control group for measuring iterative improvements during refactoring.