testing-skills-with-subagents

Run RED-GREEN-REFACTOR tests to validate skill documentation under pressure.

4|Updated Oct 3, 2025
One-click install
npx skills add https://github.com/apexbusiness-systems/APEX-OmniHub --skill testing-skills-with-subagents-apexbusiness-systems
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-skills-with-subagents
Source: https://github.com/apexbusiness-systems/APEX-OmniHub/tree/main/.cursor/superpowers/skills/testing-skills-with-subagents
Command: npx skills add https://github.com/apexbusiness-systems/APEX-OmniHub --skill testing-skills-with-subagents-apexbusiness-systems

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a structured, TDD-inspired framework for validating new or edited skills by running RED-GREEN-REFACTOR style tests on process documentation, ensuring resilience before deployment.

Core Features & Use Cases

  • RED Phase: Baseline testing without the skill to reveal real failures.
  • GREEN/REFACTOR Phases: Write minimal skill to address failures, then iterate to close loopholes.
  • Meta-testing: Re-test and document how to improve the skill and its documentation.

Quick Start

  • Review a baseline scenario WITHOUT the skill and document exact failures verbatim.
  • Create a minimal GREEN skill addressing the observed failures and re-run the scenario WITH the skill.
  • Perform a REFACTOR cycle to close new rationalizations and re-verify 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 validate skill documentation before deployment?

Testing skills with TDD involves a RED phase to baseline failures without the skill, a GREEN phase to write minimal fixes, and a REFACTOR phase to close loopholes and re-verify. This lifecycle ensures resilience before deployment.

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

The RED-GREEN-REFACTOR process for skill validation involves documenting baseline failures verbatim, creating a minimal skill to address them, and iterating to close new rationalizations. This ensures durable compliance without ad hoc checks.

How do I test process documentation under pressure?

Testing process documentation under pressure requires applying baseline pressure scenarios to reveal real failures, then iteratively improving the skill to capture exact rationalizations. This verifies durable compliance before deployment.

Why does ad hoc skill validation fail to catch rationalizations?

Ad hoc skill validation fails because it does not enforce capturing exact rationalizations under baseline pressure scenarios. Structured RED-GREEN-REFACTOR testing iteratively closes loopholes and verifies durable compliance.

Do I need dependencies to run TDD tests on skill documentation?

No dependencies are required to run TDD tests on skill documentation. The framework operates independently using baseline pressure scenarios to reveal failures and verify durable compliance through iterative improvements.