design-tracker

You can automatically document architecture decisions by using a skill that proactively captures technical choices from conversational context and updates a central DESIGN.md file. It logs implementation plans, pattern choices, and library selections without requiring manual prompts.

Tracking technical decisions is best handled by a centralized documentation system that records architectural choices and rationales as they occur. This ensures project design decisions are systematically captured and added to a changelog for future reference.

Yes, you can update project design documentation from natural language conversations. The skill uses natural language understanding to identify technical decisions made during discussions and automatically writes them into the project's design documentation.

Automatic decision tracking requires a file system interface to manage documentation effectively. It needs access to create and update a central DESIGN.md file and maintain the associated changelog based on the tracked architectural decisions.

You need automatic design decision logging when you want to systematically record architectural choices and technical rationales without manual prompting. It is essential for preserving the context of implementation plans and pattern choices during active project development.