writing-skills

Test-driven development for process documentation uses RED-GREEN-REFACTOR cycles to create baseline failures and refine skill drafts. This uncovers and closes gaps in the documentation, ensuring clarity and consistency before deployment.

Validating skills documentation against rationalizations requires running RED-GREEN-REFACTOR iterations on your drafts. This structured approach tests the documentation for guardrails and verifies it resists rationalizations before release.

Structuring a SKILL.md file requires YAML frontmatter with name and description fields. You then document the skill body following the provided structure, optionally referencing scripts, references, and assets for extended guidance.

Yes, authoring skills can reference optional scripts, references, and assets for extended guidance. These components complement the required YAML frontmatter and skill body in the SKILL.md file to centralize core principles for reuse.

TDD-based skill creation is needed when authoring or editing skills to ensure quality assurance. It provides a structured process to verify documentation drafts, enabling testing with baseline failures and refinements before deployment.

Skills documentation needs verification and iteration to ensure it resists rationalizations during deployment. Applying a test-driven approach enables testing of drafts with baseline failures and refinements, ensuring guardrails are in place before release.