achieve-documentation-completeness

Documentation completeness improves by generating structured READMEs, inserting WHY-based code comments, maintaining current API docs, and recording memory-bank decisions to preserve context for future maintainers.

The best way to write code comments is using a WHY-based approach that captures decision rationale and trade-offs, rather than just describing what the code does, ensuring context is preserved for future development teams.

Generate a comprehensive README by following structured patterns that explicitly explain the component's purpose, setup instructions, usage examples, tests, and troubleshooting guidance for new contributors.

Maintain API documentation and decision records by storing them in a memory bank, ensuring current API docs and documented decisions are preserved for future maintainers across development teams.

Yes, this approach works for large codebases by applying memory-bank decisions across development teams, ensuring coherent docs and preserved context for new contributor onboarding.