log-decision

To document architecture decisions, record the problem, decision, rationale, and consequences. This Skill gathers context and appends a formatted entry to decisions.md to preserve technical trade-offs and maintain traceability.

Logging technical design trade-offs is best handled by appending formatted entries to a decisions.md file. This captures context and consequences, allowing teams to reference and justify architecture changes during reviews or audits.

Yes, you can use it to record post-hoc justification. It gathers the required context, rationale, and consequences, then updates related guidance files to ensure the historical technical decision is fully traceable.

An architecture decision log in markdown is structured by appending formatted entries to decisions.md. The Skill prompts you for the problem, decision, rationale, and consequences, then automatically formats and persists the entry.

No dependencies are required to capture architecture context. The Skill operates independently to gather context, read decisions.md, append the formatted entry, and update related guidance files without external dependencies.