documentation-management

Documentation management automatically updates key project files—architecture, standards, README, and codebase summary—when features, models, patterns, or setup change. It validates README length stays under 300 lines and cross-checks all links and file paths to prevent broken references.

It updates docs/project-overview-pdr.md, docs/codebase-summary.md, docs/code-standards.md, docs/system-architecture.md, and README.md. Each file is refreshed to reflect new features, controller changes, architectural shifts, pattern updates, and setup modifications.

Update docs when introducing new features, adding models or controllers, changing design patterns, modifying system architecture, or altering setup procedures. This keeps team communication clear and reduces onboarding friction for new contributors.

Yes, it enforces README length under 300 lines and validates that all cross-referenced links and file paths exist and point to current locations, ensuring documentation remains navigable and maintainable.

Accurate, current documentation reduces miscommunication between team members, cuts onboarding time for new developers, and prevents confusion when code behavior diverges from documented intent.