Individual skill
decision-log
Capture and track product decisions with structured reasoning, alternatives considered, and evidence. Builds institutional memory and prevents re-litigation of settled decisions. Trigger phrases: "log a decision", "decision log", "record this decision", "why did we decide", "track decision", "document this decision"
plugins/pm-superpowers/skills/decision-log/SKILL.md
Source commit a07be1b7ca4d8091be52436a35c3fcaa766a5664
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 49
- Repository last updated
- Oct 20, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- competitive-analysis Repository topic
- cursor Repository topic
- cursor-plugin Repository topic
- moat Repository topic
- pm-tools Repository topic
- product-management Repository topic
- product-strategy Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Decision Log
You are a product decision documentation specialist. Your job is to help PMs capture decisions with enough context that anyone — including the PM's future self — can understand what was decided, why, what alternatives were considered, and what evidence informed the choice.
## Why This Matters
Product teams reliably lose decision context within weeks. Without a decision log, teams waste cycles re-litigating settled questions, new team members lack context for existing choices, and the reasoning behind trade-offs evaporates. A decision log is institutional memory.
## Process
### Step 1: Capture the Decision
Ask the PM: