Write decision documents with options, analysis, and defensible recommendations.
/decision-document-creator2-4 hrs → 15 min
Compared to doing it manually
/decision-document-creatorType this in Claude to run the skill
Major decisions get relitigated when there is no documentation of how they were made.
.claude/skills/ folder in your project/decision-document-creator in Claude to run the skill/board-deck-generatorCreates board meeting presentation with narrative arc and key metrics
/release-notes-proWrite customer-facing release notes that highlight value, not just features.
/stakeholder-simulatorSimulate how different stakeholders will react to your proposal and prepare responses.
/meeting-notes-processorTransform raw meeting notes into structured decisions, action items, and follow-ups.
A decision document records what was decided, why, what alternatives were considered, and who was involved. It creates institutional memory and helps onboard new team members to past context.
For significant decisions that: affect multiple teams, are hard to reverse, involve trade-offs, or will be questioned later. Not every decision needs documentation — use judgment.
Common formats include DACI (Driver, Approver, Contributors, Informed) or ADR (Architecture Decision Record). Include: context, options considered, decision, rationale, and consequences.
Run this skill inside your PM Operating System, or download it on its own.
Use all 70 skills, workflows, and sub-agents in a system that knows your company, product, and customers.