docs

To keep user-facing documentation aligned with feature behavior, verify current implementation against existing docs, rewrite outdated sections, and prune obsolete content from USER_GUIDE.md and README.md. Living-docs discipline ensures documentation reflects actual user flows and API references accurately.

The Diátaxis framework classifies documentation into four types: tutorials, how-to guides, references, and explanations. Applying Diátaxis-based content classification helps structure onboarding guides and API references by user intent, ensuring documentation serves learning, guidance, technical description, and analysis needs.

To remove outdated content from README.md and USER_GUIDE.md effectively, apply content pruning and revision workflows. Verify implementation against current behavior, classify content using Diátaxis, then rewrite or delete obsolete sections to maintain living documentation that reflects actual features.

This documentation update workflow requires no external dependencies or components. It operates as a standalone revision workflow to verify implementation, apply Diátaxis content classification, and refresh user-facing documentation without additional environment setup or package installations.

The best way to maintain living documentation for onboarding guides and API references is applying continuous revision workflows. Verify implementation changes, classify content updates using the Diátaxis framework, and prune obsolete sections to ensure all user-facing documentation stays synchronized with actual feature behavior.

Use living-docs discipline when feature changes leave documentation out of sync with actual behavior. This approach is essential whenever implementation updates require corresponding verification and revision of user guides, API references, and onboarding materials to prevent documentation drift and maintain accuracy.