writing-skills

Apply TDD with RED-GREEN-REFACTOR cycles to author and verify agent skills.

5|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/russosalv/NONoise --skill writing-skills-russosalv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/russosalv/NONoise/tree/main/packages/skills/vendor/superpowers/skills/writing-skills
Command: npx skills add https://github.com/russosalv/NONoise --skill writing-skills-russosalv

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Many skills and process documents are never tested, allowing agents to rationalize workarounds and ignore required workflows; this skill applies a TDD-style approach to skill authoring so agents follow documented rules under real pressure.

Core Features & Use Cases

  • TDD for documentation: RED-GREEN-REFACTOR cycle applied to SKILL.md authoring so each skill is validated with failing baseline scenarios, minimal targeted fixes, and iterative loophole closure.
  • Pressure testing with subagents: Templates and test formats for running realistic, multi-pressure scenarios (time, sunk cost, authority) and capturing verbatim rationalizations to drive precise fixes.
  • Discovery & CSO guidance: Advice on frontmatter, concise descriptions, keyword coverage, and progressive disclosure so agents reliably find and load the right skill when needed.
  • Use Cases: Creating new skills, editing discipline-enforcing skills (TDD, verification), and verifying skills before deployment to ensure agent compliance.

Quick Start

Run a pressure scenario without the skill to record failures, author SKILL.md addressing those failures, then re-run the scenario with the skill to verify compliance.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I test agent skills to prevent rationalization and ignored workflows?

Apply test-driven development to process documentation by running pressure-test scenarios with subagents to capture rationalizations, then iteratively fixing SKILL.md files to close loopholes. This enforces compliant agent behavior under real pressure.

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

The RED-GREEN-REFACTOR cycle for skill authoring involves recording baseline failures without the skill, authoring minimal targeted fixes in SKILL.md, and iteratively closing rationalization loopholes to verify agent compliance.

How do I write YAML frontmatter for agent skills?

Write YAML frontmatter containing the skill name and description to ensure reliable discovery. Optimize concise descriptions and keyword coverage so agents correctly find and load the skill when needed.

How do I pressure test documentation before deploying agent skills?

Pressure test documentation by running realistic multi-pressure scenarios involving time, sunk cost, and authority constraints using subagents. Capture verbatim rationalizations from these tests to drive precise fixes in your skills.

Does test-driven documentation work for editing existing TDD skills?

Yes, test-driven documentation works for editing existing discipline-enforcing skills like TDD and verification workflows. Use iterative testing to verify compliance and close rationalization loopholes before deployment.