update-docs

You can keep project documentation in sync with code by running an automated workflow that reads completed features and ADRs to refresh living docs like system.md, index.html, and glossary.md without manual edits.

Living documentation updates by reading inputs from discovery.md, system.md, completed feature folders, and ADR files, then writing refreshed Context, Container, and glossary sections back into system.md and index.html.

The best way to maintain architecture decision records alongside feature docs is to automate the extraction of ADR inputs into a living glossary and dynamic index.html sections, ensuring architecture notes stay aligned without altering source ADR files.

Yes, you can generate a current system overview for stakeholders from existing ADR and discovery files by running a documentation workflow that reads those sources and outputs updated system.md and index.html summaries.

No, you do not need to manually edit docs/system.md or docs/index.html when features change. An automated documentation process reads completed feature files and ADRs to write updates to those files directly.

Updating living documentation will not modify your original ADR source files. The process strictly reads from ADR and discovery inputs to write updates into system.md, index.html, and glossary.md, leaving source files untouched.