update-architecture

To keep architecture documentation in sync with code changes, you can automatically update markdown files by analyzing code updates and rebuilding docs from a deep understanding of the codebase.

Documenting design rationale and constraints is best handled by analyzing the codebase to capture the 'why' behind decisions, focusing on purpose, invariants, and data lifecycle to ensure accuracy.

Validate architecture markdown files against the actual codebase by performing dry walkthroughs that verify the documented data flows, components, and design rationales against the current code.

Yes, you can automatically regenerate architecture documentation after implementing a new module by analyzing the code changes to capture new components, data flows, and design rationales accurately.

Yes, this code-to-doc sync approach works without external dependencies, directly updating architecture markdown files by analyzing code changes and validating the results through dry walkthroughs.

Architecture documentation becomes outdated or misleading after code updates when it is not automatically synchronized with the codebase, failing to reflect new components and data flows.