Test-Driven Documentation

Why this matters

Test-driven documentation means turning the same flows that check the app into guides people can follow.

That gives you a few practical wins:

• Guides stay trustworthy. What you see is tied to checks that actually pass, so pages are far less likely to drift away from how the product really behaves.
• Less busywork. You are not maintaining a separate manual write-up that has to be remembered every release - when the flow changes, the guide can change with it from the same source.
• Better conversations. Feedback on a guide is feedback on what the product should do, which feeds back into the executable tests and keeps teams and users more aligned.
• Focus on the right things. The checks focus on outcomes that matter to users, not on internal wiring, so you can refactor and evolve the implementation with more confidence that the important behavior still holds.

How-To Guides

These pages are generated automatically from executable doc scenarios.

• Create a project and add your first task (1/11/2026)
• Create project and task (5/4/2026)