decision-log-entry

To record meeting decisions with rationale, you capture the options considered, accepted tradeoffs, revisit conditions, and participants. This creates durable markdown decision records saved to a date+slug path under product-development/product/decisions.

Preserving fast-moving product decisions is done by creating quick lightweight entries that record the decision summary alongside the driving context. This ensures the team's past why is captured without requiring a full debated options analysis.

Yes, decision logging handles superseded or reversed statuses by updating the entry file metadata. It also supports pending forward references, allowing teams to track when a previous decision is overturned by a newer meeting outcome.

Yes, decision logging supports referencing related PRDs, RFCs, and call summaries directly within the entry. This applies to both fully debated choices and quick fast-moving decisions to maintain complete decision context over time.

You organize meeting notes into a knowledge base by saving decisions to a consistent folder structure and updating the Recent Decisions list. This file-safe organization prevents merge conflicts when multiple team members log entries simultaneously.

Yes, you need YAML frontmatter containing the name and description fields to record product rationale. This metadata is required to properly index the decision entry within the product development knowledge base structure.