decision-log-guard

To log project decisions automatically, this Skill guides you through recording context, options, tradeoffs, and consequences into docs/specs/DECISIONS.md. It ensures every significant architecture, API, or workflow choice is documented using a standardized template.

A decision log governance workflow enforces disciplined documentation of significant choices to keep teams aligned and reduce rework. You need it when managing product, security, or data-model decisions that require transparent tracking and validation across a project lifecycle.

Yes, you can check new decisions for conflicts against the existing index. The Skill compares incoming choices against previously logged entries in docs/specs/DECISIONS.md to surface potential contradictions before they are officially recorded.

To document tradeoffs and consequences, follow the workflow prompts to capture required context, final decision statements, and validation evidence. Entries are created under docs/specs/decisions/entries using prescribed templates with reverse chronological updates.

The best way to maintain a reverse chronological decision log is to append new entries under docs/specs/decisions/entries and update the central index. This Skill automates that process, ensuring standardized filenames and structural consistency across all records.

Yes, you need to use the prescribed template format to record workflow and dependency decisions. The Skill enforces a specific structure requiring context, options considered, final statements, consequences, status, validation, and evidence for every logged entry.