writing-skills

Test-driven writing applies the RED-GREEN-REFACTOR workflow to documentation by running baseline RED scenarios to observe failures, drafting a minimal GREEN skill, and repeating until no new rationalizations appear to ensure robust skill deployment.

Rationalization tracking in skill writing involves building and maintaining a rationalization table and red flags to close loopholes in ambiguous rules, ensuring discipline-enforcing documentation remains consistent and reliable across deployment scenarios.

Validating skill documentation before deployment requires running RED-GREEN-REFACTOR cycles to verify real failure modes are addressed, using deployment checklists, and confirming YAML frontmatter contains required name and description fields for readiness.

Test-driven writing supports progressive disclosure patterns for scalable skills documentation by iteratively refining skill rules through RED-GREEN-REFACTOR cycles, ensuring documentation reveals complexity only as needed without ambiguous scopes.

Writing robust skills requires YAML frontmatter with name and description fields, applying RED-GREEN-REFACTOR workflows to test documentation, tracking rationalizations, and following deployment checklists to prevent untested or vague scopes.

Skill documentation often has ambiguous rules and rationalizations because it lacks test-driven development practices, allowing untested documentation and vague scopes that lead to rationalizations and deployment issues during execution.