design-tracker

Automatically document design decisions by monitoring architecture discussions and extracting choices to update your DESIGN.md file and append dated changelog entries. The system reads existing records and captures new decisions as topics arise.

A design decision log records architecture choices, patterns, and library selections in a centralized DESIGN.md file to prevent knowledge loss. You need one when project complexity grows and maintaining a consistent design narrative becomes difficult without centralized records.

Keep your changelog and design documentation current by using an automated tracker that extracts decisions from your workflow conversations. It updates relevant sections in DESIGN.md and adds timestamped changelog entries as you discuss architecture patterns and library selections.

Yes, you can query your current project architecture by asking "what's our current design?" against your DESIGN.md file. The tracking system maintains a centralized design journal that provides up-to-date summaries of recorded decisions and patterns.

Yes, this design tracking approach works without additional dependencies or components. It operates by reading your existing DESIGN.md file, extracting new information from conversations, and updating the documentation and changelog directly within your project environment.