testing-skills-with-subagents

Applies RED-GREEN-REFACTOR cycle to validate skill documentation and robustness.

2|Updated Feb 16, 2026

Search Tags:#testing #TDD #process documentation #RED-GREEN-REFACTOR #skill verification

Ready to run

npx skills add https://github.com/vivshaw/nous --skill testing-skills-with-subagents-vivshaw

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-skills-with-subagents
Source: https://github.com/vivshaw/nous/tree/main/plugins/meta/skills/testing-skills-with-subagents
Command: npx skills add https://github.com/vivshaw/nous --skill testing-skills-with-subagents-vivshaw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that skills are robust by applying the RED-GREEN-REFACTOR cycle to verify they work under pressure and resist rationalization.

Core Features & Use Cases

RED-GREEN-REFACTOR Cycle: Apply TDD principles to process documentation, ensuring compliance and effectiveness.
Baseline Testing: Run scenarios without the skill to observe failures and rationalizations.
Skill Development: Create and refine skills based on observed failures and rationalizations.
Use Case: Before deploying a new skill, use this process to ensure it will work effectively in real-world scenarios.

Quick Start

Run the skill testing process on your new skill to verify its robustness 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 verify process documentation robustness using TDD?▼

Baseline testing observes system failures and rationalizations by running scenarios without the skill applied. This establishes a control group to identify exactly which failure modes the skill needs to prevent.

How do I apply the RED-GREEN-REFACTOR cycle to skill verification?▼

Apply the RED-GREEN-REFACTOR cycle by baseline testing failures without the skill, writing skill instructions to fix those failures, pressure testing for loopholes, and refactoring the documentation to close them.

What is the best way to prevent rationalization in process documentation?▼

The best way to prevent rationalization is through pressure testing. By creating realistic test scenarios that attempt to bypass the rules, you identify loopholes in the documentation and refactor it to close them.

Do I need prior TDD knowledge to use the RED-GREEN-REFACTOR cycle for skills?▼

Yes, you need an understanding of Test-Driven Development principles and the ability to create realistic test scenarios to effectively apply this cycle to process documentation and skill verification.

When should I test skills under pressure before deployment?▼

You should test skills under pressure before deploying any new skill. This ensures the process documentation will work effectively and maintain compliance in real-world scenarios by closing rationalization loopholes beforehand.