design-tracker

To automatically track architecture decisions, this skill reads your ongoing conversations and appends date-stamped changelog entries to a DESIGN.md file. It captures implementation plans, library choices, and rationale without manual formatting.

Maintaining a centralized design changelog is done by updating the .claude/docs/DESIGN.md file with new design decisions, TODOs, and open questions. The skill triggers during architecture discussions or when prompted to record specific decisions.

Yes, documenting design decisions requires a DESIGN.md file located at .claude/docs/DESIGN.md. The skill reads existing entries from this file and updates the appropriate sections with new, date-stamped architecture information.

To record library selection rationale, explain the choice during your conversation or explicitly prompt the skill to document it. The rationale is then automatically captured and appended to the corresponding section of your DESIGN.md file.

Yes, you can trigger automatic design documentation updates by using explicit phrases like "record this" or "document this". The skill detects these prompts, extracts the design decision, and updates the changelog in DESIGN.md.

Tracking design decisions through automated conversation parsing is limited to text-based architecture discussions and requires the .claude/docs/DESIGN.md file to exist. It updates specific sections and does not generate entirely new architecture frameworks.