udocument

To clean up stale content in technical documentation, apply structured writing rules that detect and delete outdated statements misaligned with the current codebase. This enforces consistency by removing misleading notes and ensuring only accurate, behavior-matching guidance remains.

The best way to write maintainable docstrings and README files is to lead with the why, prefer readable lists over brittle tables, and stay terse. This ensures project documentation remains accurate, concise, and actionable during ongoing development.

Yes, you can enforce a consistent style guide across project docs, SKILL.md instructions, and agent guidance files. Applying rules like leading with the why and using concrete guidance ensures all technical writing remains structured and non-aspirational.

To rewrite a README and remove aspirational claims, enforce structured writing rules that require concrete, terse guidance and delete outdated content. Leading with the why ensures the documentation answers the four project-doc questions accurately under 200 lines.

You should avoid automated documentation cleanup when your codebase is rapidly changing without corresponding updates to inline comments or docstrings. If behavior is not yet stable, detecting and removing stale content might accidentally delete useful, temporary guidance.