testing-skills-with-subagents

Run RED-GREEN-REFACTOR testing cycles on documentation-based skills.

60|4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/dsifry/goodtogo --skill testing-skills-with-subagents-dsifry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-skills-with-subagents
Source: https://github.com/dsifry/goodtogo/tree/main/.claude/plugins/superpowers/skills/testing-skills-with-subagents
Command: npx skills add https://github.com/dsifry/goodtogo --skill testing-skills-with-subagents-dsifry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams validate new or edited skills by running a RED-GREEN-REFACTOR cycle on process documentation, starting baseline tests without the skill and iterating to close loopholes.

Core Features & Use Cases

  • Structured testing workflow: defines Red baseline, Green skill development, and Refactor iterations.
  • Verbatim rationalization capture: records agent rationalizations word-for-word to guide improvements.
  • Meta-testing flow: validates the skill’s resilience under multiple pressures and confirms improvements.
  • Use Case: Before deploying a CLAUDE.md style documentation skill, run a full test campaign to ensure agents consistently follow the skill.

Quick Start

Run a full RED-GREEN-REFACTOR test on a candidate skill to verify behavior under pressure.

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 test documentation skills like CLAUDE.md to ensure agents follow them under pressure?

The RED-GREEN-REFACTOR workflow defines a Red baseline without the skill, Green skill development, and Refactor iterations to systematically validate process documentation and ensure bulletproof agent performance.

How do I capture and track agent rationalizations during skill testing?

You can capture agent rationalizations by recording their responses word-for-word during simulated pressure scenarios, using these verbatim failures to guide targeted refactoring and close documentation loopholes.

Can I use this RED-GREEN-REFACTOR testing workflow for any process documentation?

Meta-testing validates the skill's resilience by applying multiple pressures and confirming improvements, ensuring the documentation skill remains bulletproof across various simulated scenarios before deployment.

What is the best way to close loopholes in process documentation?

The best way to close loopholes is to iterate through Refactor phases using captured verbatim rationalizations, applying meta-testing prompts to validate resilience and ensure agents cannot bypass the documentation rules.