writing-skills

Write and test Skills using RED-GREEN-REFACTOR cycles on process documentation.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/xfs96192/claude-config --skill writing-skills-xfs96192
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/xfs96192/claude-config/tree/main/plugins/cache/claude-plugins-official/superpowers/5.0.7/skills/writing-skills
Command: npx skills add https://github.com/xfs96192/claude-config --skill writing-skills-xfs96192

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing Skills provides a test-driven approach to documenting skills, turning ad-hoc guidance into verifiable, reusable references that resist rationalization and ensure agents follow intended behavior.

Core Features & Use Cases

  • TDD-driven Skill docs: apply red-green-refactor to Skill documentation
  • Discipline against rationalizations: explicit countermeasures like rationalization tables and red flags
  • Progressive disclosure patterns: structure SKILL.md to load heavy references only when needed
  • Testing and deployment readiness: guides for RED-GREEN-REFACTOR, testing workflows, and deployment checks

Quick Start

Draft a new SKILL.md using the standard template, then run the RED-GREEN-REFACTOR testing loop to validate it.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I write process documentation that stops agents from rationalizing instructions?▼

To stop rationalization, write process documentation using a test-driven approach with explicit countermeasures like rationalization tables and red flags. This transforms ad-hoc guidance into verifiable references that enforce intended agent behavior.

What is the RED-GREEN-REFACTOR cycle for testing skill documentation?▼

The RED-GREEN-REFACTOR cycle is a TDD method for testing skill documentation. You draft a SKILL.md, run the testing loop to validate baseline behavior, and refine the docs until they pass robust deployment readiness checks.

How do I structure SKILL.md files to load heavy references only when needed?▼

Progressive disclosure patterns structure SKILL.md files to load heavy references only when needed. This technique keeps metadata concise and ensures agents retrieve dense contextual information dynamically during execution.

Does a test-driven approach to skill writing require any external dependencies?▼

A test-driven approach to skill writing requires no external dependencies. It relies entirely on a standard SKILL.md template and internal RED-GREEN-REFACTOR workflows to validate and refine documentation.

What is the best way to validate skill documentation before deployment?▼

The best way to validate skill documentation before deployment is running the RED-GREEN-REFACTOR testing loop. This process verifies baseline behavior, captures rationalizations, and ensures robust testing readiness.

When should I not use TDD-guided documentation for skills?▼

Avoid TDD-guided documentation when ad-hoc guidance is sufficient and rationalization risks are low. If progressive disclosure and strict deployment checks are unnecessary, standard documentation methods without red flags may be more efficient.