design-tracker

To automatically record architecture decisions, you can use a tool to capture choices during discussions and append structured, dated entries directly into your project's DESIGN.md file and changelog.

Design traceability is the practice of preserving architecture rationale. It is needed to ensure that library selections, implementation plans, and pattern choices are documented for future reference without manual note-taking.

You maintain a design log by recording decisions as they occur during architecture discussions. The tool automatically reads and updates DESIGN.md, appending a dated changelog entry for each captured decision.

Yes, you can document library and pattern selections in DESIGN.md. The tool automatically captures these selections as they happen and updates the design documentation with structured entries for future reference.

Automatic decision capture works by proactively recording architecture choices, implementation plans, and library selections as they occur, ensuring rationale is preserved in DESIGN.md without requiring manual note-taking.

You should avoid automated design documentation if your project lacks a docs/DESIGN.md file or if your workflow does not involve formal architecture discussions, library selections, or implementation planning that requires rationale tracking.