record-decision

To record project decisions into a structured markdown workflow, you capture summaries, technical details, commits, and unresolved items into a single source of truth documentation format. This ensures session outcomes are consistently organized and not lost.

A single source of truth documentation process organizes project decisions and session outcomes into consistent markdown files. It separates detailed technical records from concise daily logs to prevent important architectural changes from being lost.

To update repository documentation when architecture changes, you review existing docs against new specifications during your development session. This process checks if repository documentation requires updates and appends concise summaries to daily activity logs.

Yes, you can separate detailed decision records from daily project logs. The workflow appends concise session summaries with references to detailed decision files, keeping daily logs lightweight while preserving technical details and unresolved items.

The best way to track unresolved items and session outcomes is creating structured decision files containing summaries, technical details, commits, and unfinished tasks. This records exactly what was changed, why it was decided, and what remains.