decision-doc

Generate structured product decision documents with options, trade-offs, and recommendations.

1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill decision-doc-kalilurrahman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-doc
Source: https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts/tree/main/09-product-management/decision-doc
Command: npx skills add https://github.com/kalilurrahman/kr-claudiator-skills-original-prompts --skill decision-doc-kalilurrahman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Product decisions often stall in ambiguity or get made without documented reasoning, leaving stakeholders without a clear record of options considered and trade-offs accepted. This Skill turns a vague decision into a one-page document with framed context, evaluated options, and a defensible recommendation. ## Core Features & Use Cases - Structured Decision Framing: Captures context, constraints, and the cost of doing nothing before evaluating options. - Option Evaluation: Compares 2-4 genuinely distinct options across pros, cons, effort, risk, and reversibility, including a comparison table. - Explicit Recommendation: Forces a clear pick with stated trade-offs, reversibility analysis, and owner-assigned next steps. - Use Case: A product manager debating whether to build an in-house feature, buy a vendor solution, or defer the work can produce a stakeholder-ready decision doc in one pass. ## Quick Start Ask the AI to create a decision doc for whether to migrate the mobile app to a cross-platform framework or keep native development.

Frequently Asked Questions about decision-doc

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a product decision document?

Frame the decision and its constraints, generate 2-4 genuinely distinct options, evaluate each on pros, cons, effort, risk, and reversibility, then make an explicit recommendation with next steps. Keep the document to one page so stakeholders can review it quickly.

What should a decision doc include for stakeholder review?

A decision doc should include context, constraints, evaluated options with a comparison table, a clear recommendation, the trade-offs being accepted, reversibility analysis, and owner-assigned next steps. Omitting the recommendation or trade-offs makes it a menu, not a decision.

How many options should a decision document compare?

Compare 2-4 options maximum, and include 'do nothing' when inaction is genuinely viable. More than four options signals the problem has not been narrowed enough, and each option must be genuinely different rather than a variation of the same idea.

When should I not use a one-page decision doc?

Avoid it when the input is too vague to generate meaningful options, in which case clarifying questions come first. If the document exceeds two pages, the decision is likely two separate decisions that should be split and analyzed independently.

Why does a decision doc need a reversibility section?

Reversibility determines how much analysis a decision deserves. Irreversible decisions warrant deeper scrutiny, while reversible ones should be made faster, so the document must state whether course correction is possible, at what cost, and by when.