Decision Log — Bundle

The problem

Teams and solo founders often re-litigate the same choices every few months because the original rationale was never documented. This leads to circular debates, meeting fatigue, and "decision debt" where nobody remembers why a specific path was chosen.

What it does

• Classifies decisions as one-way or reversible to calibrate the weight of the evaluation process.
• Forces the documentation of at least two viable options, including honest strengths of rejected paths.
• Defines specific "falsifiers" or triggers that would justify reopening a settled matter.
• Quotes previous records when a topic is re-raised to ensure new arguments are based on changed facts.
• Enforces strict one-page brevity to prevent decision logs from bloating into unreadable strategy docs.

Why this beats prompting it yourself

Standard LLMs tend to be overly agreeable and avoid friction. This skill acts as a disciplined archivist that refuses to accept "gut feelings" and demands structural proof, preventing the generic "it depends" responses that stall actual progress.

Use cases

• Documenting product pricing changes to prevent future second-guessing.
• Recording architectural choices in software development for future onboarding.
• Evaluating high-stakes hires or vendor selections with clear rejection criteria.
• Setting dated triggers to review experimental features or marketing pivots.

Known limitations

Does not provide legal, tax, or medical advice. It functions as a structured record-keeper and logic-checker, not a mediator for live interpersonal conflicts.