writing-skills

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

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/Sungmaster/Sung --skill writing-skills-sungmaster
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/Sungmaster/Sung/tree/main/.claude/plugins/superpowers/skills/writing-skills
Command: npx skills add https://github.com/Sungmaster/Sung --skill writing-skills-sungmaster

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of inconsistent or ineffective agent documentation by applying Test-Driven Development (TDD) principles to the creation and maintenance of process guides.

Core Features & Use Cases

  • TDD for Documentation: Provides a structured RED-GREEN-REFACTOR cycle to ensure skills are tested against real-world pressure scenarios before deployment.
  • Rationalization Countering: Includes frameworks to identify and neutralize agent rationalizations that lead to rule-breaking.
  • Use Case: Use this when you need to create a new skill or update an existing one to ensure it is bulletproof, verifiable, and resistant to being ignored by the agent under stress.

Quick Start

Use the writing-skills framework to create a new skill by first running a baseline pressure scenario to document how the agent fails without the skill.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I use TDD to write process documentation?

Use TDD for process documentation by running a baseline pressure scenario to capture failures, then applying a RED-GREEN-REFACTOR cycle to build and verify compliant skills. This ensures your process guides are bulletproof and tested against real-world stress before deployment.

What is the RED-GREEN-REFACTOR cycle for compliance documentation?

The RED-GREEN-REFACTOR cycle for compliance documentation is a Test-Driven Development framework where you write failing tests for pressure scenarios, create process guides to pass them, and refactor to eliminate agent rationalizations that lead to rule-breaking.

How do I prevent agents from ignoring process documentation under pressure?

Prevent agents from ignoring process documentation under pressure by applying a TDD framework that uses pressure scenarios to validate skill effectiveness and includes mechanisms to identify and neutralize agent rationalizations that lead to rule-breaking.

When should I use a test-driven development approach for creating agent skills?

Use a test-driven development approach for creating agent skills when your process documentation requires high compliance under pressure. It is essential when you need to ensure new or updated skills are verifiable, bulletproof, and resistant to being ignored by agents under stress.

Does this TDD documentation framework work without external dependencies?

Yes, this TDD documentation framework works without external dependencies. It relies entirely on internal scripts to implement the RED-GREEN-REFACTOR cycle and validate process compliance, requiring no additional packages or external libraries to verify skill effectiveness.

What is the best way to validate that a process guide remains effective during stress scenarios?

The best way to validate process guide effectiveness during stress scenarios is to implement a Test-Driven Development framework that requires adherence to the RED-GREEN-REFACTOR cycle, testing documentation against baseline pressure scenarios before deployment.