documentation-driven-development

What problem does it solve?

It prevents undocumented or incorrectly documented features from quietly drifting into your product by enforcing documentation-first development, then verifying the docs via tests.

Core Features & Use Cases

• Documentation-first feature definition: Decide and write how the feature should work from the user’s perspective before implementing it.
• Test the documentation’s truth: Create unit tests that reflect the documented behavior so mismatches fail loudly.
• Documentation-led changes: When modifying an existing feature, update the documentation first and then update the corresponding tests to stay aligned.
• Use a documentation framework for clarity: Apply reference materials (e.g., Divio’s tutorial/how-to/reference/explanation structure) and writing/Markdown style guidance to keep docs consistent and discoverable.

Quick Start

Use this skill when you are about to build or change a feature and want to ensure the behavior you ship is exactly what your documentation claims.