writing-skills

Enforce RED-GREEN-REFACTOR testing on agent skill documentation before publication.

1|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/Domush/react-skills --skill writing-skills-domush
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Domush/react-skills/tree/main/skills/writing-skills
Command: npx skills add https://github.com/Domush/react-skills --skill writing-skills-domush

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents undocumented, rationalized skill releases by forcing RED-GREEN-REFACTOR testing before publication and keeping every new or updated skill aligned with agent behavior under pressure.

Core Features & Use Cases

  • Discipline-enforcing TDD: Capture failing baselines, write minimal guidance, and add explicit counters for every rationalization before agents touch production skills.
  • Pressure testing playbook: Run multi-pressure scenarios to document rationalizations, build red flags, and verify compliance when creating new skills, editing existing ones, or deploying updates.
  • Discovery and reference guidance: Define symptom-based descriptions, reference placement, and cross-references so Claude finds the skill without loading unnecessary content.

Quick Start

Ask writing-skills to test new documentation with RED-GREEN-REFACTOR pressure scenarios before publishing.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
What is TDD for agent skill documentation?

TDD for agent skill documentation is a discipline-enforcing process that captures failing baseline pressure scenarios, writes minimal guidance, and adds explicit rationalization counters before publication to verify compliance.

How do I pressure-test process documentation before publishing?

You pressure-test process documentation by running multi-pressure scenarios to document rationalizations, build red flags, and apply explicit rule enforcement using a RED-GREEN-REFACTOR testing cycle before release.

Why do agents rationalize skipping checks in skill documentation?

Agents rationalize skipping checks when operating under pressure, bypassing required validation steps. Rationalization tables and red flags capture these specific bypasses to enforce explicit rule compliance during skill creation or edits.

Can I use TDD pressure testing for editing existing skills?

Yes, you can use TDD pressure testing when creating new skills, editing existing ones, or deploying updates. It requires baseline pressure scenarios and rationalization tables to verify compliance before publication.

What's the best way to prevent untested agent skill releases?

The best way to prevent untested agent skill releases is locking documentation behind RED-GREEN-REFACTOR pressure testing, requiring failing baselines, rationalization counters, and explicit rule enforcement before declaring compliance.

Do I need rationalization tables for discipline-enforcing skills?

Yes, rationalization tables are required for discipline-enforcing skills. They document specific rationalizations agents use to skip checks under pressure, establishing red flags and explicit rule enforcement before compliance is declared.