writing-skills

Define TDD-based process documentation for Claude-style skill docs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ctrlShiftBryan/dotfiles --skill writing-skills-ctrlshiftbryan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/ctrlShiftBryan/dotfiles/tree/main/claude/.claude/skills/writing-skills
Command: npx skills add https://github.com/ctrlShiftBryan/dotfiles --skill writing-skills-ctrlshiftbryan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Writing robust, reusable process documentation for skills that can be tested and iterated using TDD principles.

Core Features & Use Cases

  • TDD-driven documentation: Apply red-green-refactor discipline to craft skills that are testable and evolvable.
  • Rationalization tracking: Include explicit rationalizations and counters to prevent slipping under pressure.
  • Discovery-friendly design: Structure content for fast loading, progressive disclosure, and easy cross-referencing.

Quick Start

Draft a new Writing Skills SKILL.md that demonstrates a TDD-based approach to documenting processes.

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 writing process documentation?▼

Test-driven development for process documentation applies red-green-refactor discipline to skill creation, ensuring docs are testable and evolvable through explicit testing and rationalization tracking before finalizing the content.

What is rationalization tracking in skill development?▼

Rationalization tracking in skill development involves including explicit rationalizations and counters within process documentation to prevent the skill from slipping or deviating from its intended logic under pressure.

How do I structure Claude skills for fast loading and discovery?▼

Structure Claude skills for discovery by using progressive disclosure and easy cross-referencing, which prompts loading of minimal, targeted references as needed rather than loading the entire document at once.

What's the best way to make process documentation repeatable and testable?▼

The best way to make process documentation repeatable is to ground it in test-driven development principles, applying red-green-refactor discipline to iterate on skill docs until they produce consistent, tested outcomes.

Do I need prior TDD experience to document skills with this approach?▼

Prior TDD experience is not strictly required, but understanding red-green-refactor discipline helps you craft testable skills, as the technique explicitly emphasizes applying these development principles to process documentation.

When should I avoid using TDD for skill documentation?▼

You should avoid TDD for skill documentation when a process is purely exploratory or one-off, since the approach requires defining explicit tests and rationalizations that add overhead suited for reusable, repeatable processes.