writing-skills

Test-driven documentation uses the RED-GREEN-REFACTOR lifecycle to draft, test, and refine process docs. You write failing tests for your documentation requirements, make them pass by writing the docs, and then refactor for clarity and reusability.

Creating skill units requires codifying structured frontmatter and body content with explicit dependencies and components. This ensures discoverability, safety, and reusability within the library while capturing baselines and rationalizations.

The RED-GREEN-REFACTOR cycle for authoring skills is a testing lifecycle. RED drafts failing tests for skill requirements, GREEN writes the skill content to pass tests, and REFACTOR refines the skill to minimize context load while staying verifiable.

To add safety checks to prevent untestable documentation, enforce explicit dependencies, components, and structured guidance during skill creation. This prevents unsafe or untestable content from entering your skills library.

Yes, test-driven skill authoring works without external dependencies. The workflow relies entirely on internal structured guidance and frontmatter codification to validate skills, requiring no external modules or packages to enforce the lifecycle.