Decision Logger

Pro v1.0.0 1 view

Transform rough decision notes into comprehensive, structured decision log entries with rationale, alternatives, stakeholders, and impact analysis.

What You Get

Reduce decision documentation time from 30-60 minutes to seconds while creating searchable institutional memory that prevents re-discussion and preserves context.

The Problem

Product managers make dozens of decisions weekly but documenting them properly takes 30-60 minutes each. Most decisions go undocumented, leading to repeated discussions, lost context when team members leave, and inability to learn from past choices. Meeting notes are scattered across tools and lack structure for future reference.

The Solution

Converts rough decision notes (meeting bullets, memory, informal notes) into comprehensive decision log entries with standardized format. Extracts decision summary, rationale, alternatives considered, expected impact, success criteria, and review dates. Marks incomplete sections for verification and outputs entries ready for any decision log system.

How It Works

  1. 1 Provide rough notes about the decision including what was decided, who was involved, and why
  2. 2 Skill structures notes into comprehensive decision log format with all standard sections
  3. 3 Review generated entry, fill any marked sections needing verification, paste into your decision log

What You'll Need

  • Notes about the decision (can be rough bullets, meeting notes, or memory)
  • Context on who was involved and why the decision was made

Get This Skill

Requires Pro subscription ($9/month)

Have Feedback?

Help us improve this skill by sharing your ideas and suggestions.

Request Improvements

Examples

Launch Delay from Sparse Meeting Notes

Documents a Q4 launch delay decision from very minimal notes. Demonstrates how the skill handles sparse input by creating reasonable structure and marking many sections for verification. Also captures team dissent (Sarah disagreed) appropriately.

View example

Mobile App Sunset with Financial Analysis

Documents a strategic decision to sunset a mobile app in favor of web-only. Shows handling of financial data ($400K savings), usage metrics (8% mobile users), and multiple alternatives. Demonstrates appropriate [To be filled] markers for missing implementation details.

View example

Technical Framework Selection

Documents a frontend framework decision (React vs Vue) with minimal input. Demonstrates how the skill infers reasonable structure from brief notes and creates comprehensive rationale around ecosystem and hiring considerations.

View example
View all examples