writing-skills

Create and refine AI skills documentation using a test-driven RED-GREEN-REFACTOR cycle.

Updated Mar 6, 2026
One-click install
npx skills add https://github.com/ryan-ressmeyer/llm-skills --skill writing-skills-ryan-ressmeyer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/ryan-ressmeyer/llm-skills/tree/main/writing-skills
Command: npx skills add https://github.com/ryan-ressmeyer/llm-skills --skill writing-skills-ryan-ressmeyer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a rigorous, test-driven framework for creating and refining documentation skills, ensuring they are discoverable, effective, and resistant to misuse.

Core Features & Use Cases

  • Test-Driven Skill Development: Apply the RED-GREEN-REFACTOR cycle to skill documentation.
  • Rationalization Countermeasures: Explicitly address and prevent common excuses agents use to bypass documentation.
  • Use Case: When developing a new skill for code review, use this framework to first demonstrate how an agent fails without the skill (e.g., skips reviews under time pressure), then write the skill to prevent that specific failure, and finally test it under pressure to ensure it holds.

Quick Start

Use the writing-skills skill to create a new skill document following test-driven principles.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I apply test-driven development to AI skill documentation?

Test-driven skill documentation applies the RED-GREEN-REFACTOR cycle by first demonstrating how an agent fails without the skill, writing the skill to prevent that failure, and pressure testing it for compliance.

How do I prevent AI agents from bypassing documentation under pressure?

Prevent AI agents from bypassing documentation under pressure by implementing rationalization countermeasures, explicit rules, and pressure testing to enforce strict discipline and compliance during skill creation.

What is the best way to structure AI agent compliance rules in skill development?

The best way to structure AI agent compliance rules is through rationalization tables that explicitly address common excuses agents use to bypass documentation, ensuring strict adherence to process under pressure.

When do I need to use a test-driven framework for creating agent skills?

You need a test-driven framework for creating agent skills when you require strict adherence to process, high documentation quality, and resistance to agent misuse or rationalization under time pressure.

Can I pressure test AI skills against rationalization before deployment?

Yes, you can pressure test AI skills against rationalization before deployment by simulating scenarios where an agent might skip processes under time pressure and verifying the skill explicitly prevents that failure.

Why does my AI agent skip code review documentation despite existing instructions?

Your AI agent skips code review documentation due to rationalization under pressure, which requires explicit countermeasures and a test-driven skill framework to force strict adherence to the process.