ring:writing-skills

To apply TDD to process documentation, you use a RED-GREEN-REFACTOR workflow to write and validate skills. You first create a baseline pressure scenario to capture failure cases, implement the documentation, and verify it passes.

Rationalization prevention in skill writing is a discipline-first approach that captures baseline failure cases and rationalizations. It ensures process documentation is verifiable before use and prevents future missteps by applying anti-rationalization patterns.

You create baseline tests for process documentation by capturing specific failure cases and rationalizations during a pressure scenario. These baseline tests act as verification checkpoints within the RED-GREEN-REFACTOR cycle to validate the skill before use.

Yes, you can use test-driven development to verify process guides before use by applying a RED-GREEN-REFACTOR workflow. This approach requires baseline tests and iterative refinement based on test outcomes to ensure documentation is verifiable.

Iterative refinement for skill creation works by updating process documentation based on test outcomes and real usage. By repeatedly performing the RED-GREEN-REFACTOR cycle, skills are continuously improved and validated against baseline tests.

A limitation of using TDD for documentation is that it requires strict adherence to the RED-GREEN-REFACTOR workflow and baseline pressure scenarios. Without capturing specific failure cases and rationalizations, the discipline-first approach cannot effectively prevent future missteps.