writing-skills

You apply TDD to skill creation by using a RED-GREEN-REFACTOR cycle. This approach enforces discipline by writing baseline tests for process documentation first, then refining the skill to address observed failures and ensure compliance.

The best way to verify process documentation is through a testing framework that includes pressure scenarios, rationalization tables, and red flags. This ensures your writing guidelines maintain compliance and effectiveness across various skill types.

You structure skill directories by organizing files into SKILL.md, supporting references, and workflow scripts. This optimal layout facilitates the TDD cycle, allowing you to systematically test and refine techniques, patterns, and references.

Yes, you need a solid understanding of TDD principles before documenting techniques and patterns. This Skill requires applying test-driven discipline to enforce compliance, demonstrate techniques, and verify references effectively during the creation process.

Yes, you can write a baseline test to capture current behavior without the skill. This TDD approach allows you to observe failures first, then write the skill itself to address those specific gaps in process documentation.

You can create and verify techniques, patterns, and references using a test-driven documentation approach. This variety covers multiple use cases, applying discipline enforcement and pattern application to ensure effective process guidance.