update-changelog

To maintain a centralized changelog for project decisions in a markdown file, append entries to the Recent Updates and Decisions section of AGENTS.md. Include the ISO date, time, optional label, bulleted changes, and optional version information for an auditable record.

The best way to log project updates and decision history for future contributors is using a structured entry format in AGENTS.md. Append decisions with a date, time, and concise description to preserve project context and ensure traceability for onboarding.

Format a new entry in the Recent Updates and Decisions section by appending the ISO date, time, optional label, a bullet list of changes, and optional version information. This structured format ensures project history remains auditable and easy to reference.

Yes, you can track project management decisions and version notes across multiple projects. The skill works across projects by appending structured entries with dates, times, and concise descriptions to the end of each project's AGENTS.md file.

Your decision tracking log needs structured timestamps and labels to preserve project history with clear traceability. Including the ISO date, time, and optional labels ensures future contributors understand the context and rationale behind specific project updates.

You should not use AGENTS.md for logging project documentation if your workflow requires complex branching histories or non-text attachments. It is designed for concise, centralized decision tracking using structured text entries rather than comprehensive binary documentation.