writing-skills

Test-driven development for process documentation involves defining RED-GREEN-REFACTOR cycles to write, validate, and refactor skill workflows. You start by capturing a failing test for the desired behavior, create documentation to pass it, and then refactor for clarity.

To structure skill metadata for discoverability, enforce structured YAML frontmatter containing name and description, concise descriptions, and cross-references. This ensures the skill is deployment-ready, safe, and reusable across real-world scenarios.

Capture rationalizations during skill writing by using rationalization tables and red flags within your process documentation. This mechanism records edge-case decisions and deviations, ensuring discipline-enforcing skills remain consistent and reducing drift across deployments.

Skill documentation loses consistency across deployments due to a lack of a structured, validated process. Applying test-driven development to process documentation with quality assurance checks ensures verifiable tests and robust guidance that reduce drift.

Deployment-ready skills require quality checks that enforce structured frontmatter, concise descriptions, cross-skill references, and red flags. These checks ensure the final process documentation is discoverable, safe, and reusable before deployment.