writing-skills

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

Updated Aug 6, 2025
One-click install
npx skills add https://github.com/flosrn/.claude --skill writing-skills-flosrn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/flosrn/.claude/tree/main/skills/writing-skills
Command: npx skills add https://github.com/flosrn/.claude --skill writing-skills-flosrn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, test-driven approach to 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 authoring.
  • Rationalization Countermeasures: Learn to identify and block common excuses agents use to bypass documentation.
  • Use Case: You're creating a new skill for code review. Before writing the SKILL.md, you'll write test scenarios to see how an agent naturally reviews code without the skill (RED), then write the skill to enforce best practices (GREEN), and finally, test against common rationalizations like "it's faster to just commit" (REFACTOR).

Quick Start

Use the writing-skills skill when you are about to create a new skill document.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I use test-driven development for agent skill creation?

Test-driven skill creation applies the RED-GREEN-REFACTOR cycle to documentation, writing test scenarios for agent behavior first, then refining the skill to enforce best practices and resist rationalization bypasses.

What is RED-GREEN-REFACTOR methodology for documentation skills?

RED-GREEN-REFACTOR for documentation skills involves testing baseline agent behavior without the skill, writing the skill to enforce desired compliance, and then refactoring against pressure scenarios to block rationalizations.

How to stop AI agents from bypassing documentation tasks?

To stop AI agents from bypassing documentation, apply rationalization countermeasures during skill testing, identifying and blocking common excuses like claiming speed improvements to skip required steps.

What are pressure scenario tests for agent behavior?

Pressure scenario tests evaluate documentation skills by simulating edge cases where agents might deviate, ensuring the skill maintains compliance and discoverability under rationalization pressure.

When do I need to apply TDD to skill development?

You need to apply TDD to skill development before writing a new SKILL.md document, ensuring you establish baseline agent behavior first to effectively enforce and iterate on compliance.

Best way to ensure skill discoverability and compliance?

The best way to ensure skill discoverability and compliance is iterating through test-driven development, validating agent behavior against pressure scenarios to refine the documentation and prevent misuse.