writing-skills

Write process documentation using test-driven development and RED-GREEN-REFACTOR cycles.

Updated Jun 12, 2026
One-click install
npx skills add https://github.com/flowel/AiSkills --skill writing-skills-flowel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/flowel/AiSkills/tree/main/skills/codex/writing-skills
Command: npx skills add https://github.com/flowel/AiSkills --skill writing-skills-flowel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enables you to create comprehensive, effective documentation by adopting a test-driven approach to process documentation.

Core Features & Use Cases

  • Test-Driven Documentation: Write test cases for processes, watch them fail, then write the documentation (SKILL.md) to make them pass.
  • Skill Creation Guide: Offers step-by-step guidance for creating and validating skills using the RED-GREEN-REFACTOR cycle.
  • Best Practices: Provides best practices for skill authoring, including Claude search optimization (CSO) and persuasive techniques for compliance.

Quick Start

Run your_command_here to begin the skill creation process, ensuring your documentation teaches the right things and stands up to real-world scenarios.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
What is test-driven documentation and how does it apply to skill authoring?

Test-driven documentation applies TDD principles to process documentation by writing test cases for processes first, watching them fail, then writing the SKILL.md to make them pass, ensuring the documentation teaches the right things and stands up to real-world scenarios.

How do I use the RED-GREEN-REFACTOR cycle to create process documentation?

To use the RED-GREEN-REFACTOR cycle for process documentation, you write test cases for your process and watch them fail (RED), write the documentation to make them pass (GREEN), then refine the documentation for clarity and compliance (REFACTOR).

How can I make my process documentation stand up to real-world pressure tests?

You can make process documentation stand up to pressure tests by adopting a test-driven approach, writing test cases that reflect real-world challenges before creating the documentation, ensuring it effectively teaches the correct processes.

What best practices should I follow for skill authoring and documentation creation?

Best practices for skill authoring include applying Claude search optimization (CSO), using persuasive techniques for compliance, and following the test-driven RED-GREEN-REFACTOR cycle to validate that your documentation teaches the correct processes.

Do I need to understand test-driven development principles to create effective process documentation?

Yes, you need to understand test-driven development principles and effective communication techniques to use this framework, as it applies TDD concepts like RED-GREEN-REFACTOR directly to the creation and validation of process documentation.

What's the best way to validate that my skill documentation teaches the right things?

The best way to validate skill documentation is to write test cases for the processes first, watch them fail, then write the documentation to make them pass, ensuring the content reflects real-world challenges and stands up to pressure tests.