Architecture Documentation Currency Review
Check diagrams and decision records against reality.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
Review architecture docs. Diagrams, decision records and descriptions: [ARCHITECTURE_DOCS]. Current system as team members describe it: [CURRENT_SYSTEM]. Identify components, flows and dependencies that are missing or wrong, decisions that were reversed without a record, and terms used inconsistently. Check dates and owners. Return a table of discrepancies, a list of questions for the team, and a plan to refresh the docs with a review date and owner for each. Keep diagrams simple enough to maintain. Add a worked discrepancy list: the diagram shows a queue between the web app and the billing service, but billing is now called directly; the decision record says use database A, though the team moved to B a year ago; the glossary uses customer and account interchangeably. Plan a 90-minute workshop to redraw the diagram together and a calendar reminder every six months. Keep diagrams at one level of detail with a legend. Add a short rule: every pull request that changes a boundary or dependency updates the diagram or the decision record, and the reviewer checks it. Record the last verified date on every diagram.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.