writing-skills

Create and verify agent skills using the RED-GREEN-REFACTOR cycle.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill solves the problem of inconsistent, unreliable, or poorly understood documentation by applying Test-Driven Development (TDD) principles to the creation and maintenance of agent skills.

Core Features & Use Cases

  • TDD for Documentation: Provides a structured RED-GREEN-REFACTOR cycle for writing and verifying skills.
  • Rationalization Prevention: Includes techniques to identify and counter 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 robust, testable, and resistant to being ignored by future agent instances.

Quick Start

Use the writing-skills framework to create a new skill by first defining a failing pressure scenario and then documenting the minimal instructions required to ensure compliance.

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 for documentation to prevent agent rationalization?

TDD for documentation prevents agent rationalization by applying a RED-GREEN-REFACTOR cycle to skill creation, defining failing pressure scenarios first and then documenting minimal instructions to ensure strict rule compliance.

What is the RED-GREEN-REFACTOR cycle for agent skills?

The RED-GREEN-REFACTOR cycle for agent skills is a test-driven development process where you define a failing pressure scenario, write the minimal documentation to pass it, and refactor the instructions to ensure they remain bulletproof against rationalization.

How do I create a new skill using Test-Driven Development methodologies?

To create a new skill using Test-Driven Development methodologies, you start by defining a failing pressure scenario that highlights an agent's potential rationalization, then document the minimal instructions required to ensure compliance and verify the skill.

Why does my AI agent ignore documentation and break process rules?

AI agents ignore documentation and break process rules due to rationalization, which you can counter by standardizing skill creation with TDD methodologies that enforce discipline through structured testing and verification cycles.

When should I use TDD to update existing agent skills?

You should use TDD to update existing agent skills when you need to ensure the documentation is robust, testable, and resistant to being ignored by future agent instances during process execution.

Can I test agent skills for compliance without using Test-Driven Development?

Testing agent skills for compliance without Test-Driven Development lacks the structured verification needed to prevent rationalization, making TDD methodologies essential for creating bulletproof, discipline-enforcing documentation.