maintain-docs

You can automate documentation maintenance by running Python scripts like assess_doc_change.py to evaluate code changes during pre-commit checks and route updates to reference docs, keeping the main guide stable.

A progressive disclosure framework separates documentation into a stable main guide, such as AGENTS.md, and a set of evolving per-topic reference docs. This structure prevents main guides from bloating while detailed references grow independently.

Run create_reference_doc.py with the topic and when-to-read parameters to generate the doc from a template, then execute update_reference_table.py to register the new file in the Reference Documentation table and keep mappings current.

No external dependencies are required, but the workflow needs Python tooling to run the assessment, creation, and table update scripts, plus npm to run lint validation for checking the documentation and tooling setup.

You should move details into a separate reference doc when assess_doc_change.py determines the change does not belong in the main AGENTS.md file, ensuring the primary guide remains stable while reference material evolves.