util-context-advisor

To clarify design decisions from architecture docs, you need a tool that synthesizes design rationale and explains trade-offs by citing sources directly from your plans and documentation. This approach maintains traceability during planning and reviews.

Summarizing how planned components fit together requires analyzing current plans, architecture docs, and README files to extract system intent. The synthesis explains component relationships and architectural context for planning reviews.

Yes, you can get source citations when answering architecture questions by using tools that enforce source rules. Outputs cite specific locations from plans, architecture docs, README files, and CLAUDE.md to maintain traceability.

To resolve architectural questions during planning, you need current plans in plans directories, architecture docs, README/design docs, and a CLAUDE.md file. These inputs provide the context required to explain system intent and component fit.

It works directly with CLAUDE.md and plans directories by reading these files as required inputs. The tool processes these sources alongside architecture docs and README files to generate cited answers about design decisions.

Use an AI-assisted design tool for system context during planning phases and code reviews when you need to clarify how components fit together. It synthesizes design rationale and trade-offs from your existing documentation.