create-decision-log

To document engineering decisions with context, you log structured entries that capture the topic, options explored, final choice, and expected outcomes. This ensures future teams can review the exact rationale behind product and engineering choices.

The best way to create an Architecture Decision Record (ADR) is using a structured log that separates context, options, and rationale. This standardizes archival and review across product, engineering, and planning activities.

Yes, you can automatically generate numbered decision log files. The skill auto-generates a new file name based on the next available number under the designated product documentation directory.

You structure a feature proposal by logging a decision entry that explicitly separates context, chosen options, rationale, and expected outcomes. You also define revisit triggers to specify when the decision should be re-evaluated.

Yes, this decision logging approach works without external dependencies. It writes structured markdown files directly into your local documentation directory, requiring no additional components or frameworks to capture context and rationale.

You should use a structured decision log because informal planning notes often lose context over time. Structured entries ensure future teams understand the information considered, the options weighed, and the exact rationale behind the final product or engineering choice.