decision-doc

Document product decisions with rationale, alternatives, and trade-offs.

Updated Apr 10, 2026
One-click install
npx skills add https://github.com/ramybarsoum/RStack-V0 --skill decision-doc-ramybarsoum
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-doc
Source: https://github.com/ramybarsoum/RStack-V0/tree/main/skill/decision-doc
Command: npx skills add https://github.com/ramybarsoum/RStack-V0 --skill decision-doc-ramybarsoum

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Product teams frequently make strategic choices without capturing the rationale, alternatives, and trade-offs, which leads to repeated debates, lost context, and poor institutional memory. This Skill helps teams record decisions so future stakeholders understand why choices were made and who is accountable.

Core Features & Use Cases

  • Structured Decision Records: Produce decision documents that include rationale, considered alternatives, trade-offs, owners, dates, and recommended next steps.
  • Stakeholder Alignment: Guide PMs through grouped, structured questions to gather inputs from relevant stakeholders and prevent follow-up ambiguity.
  • Use Cases: Choosing build vs. buy, selecting an architecture or tech stack, resolving competing feature approaches, and documenting tradeoffs for product strategy reviews.

Quick Start

Create a decision document for choosing between two feature approaches that lists the rationale, alternatives, trade-offs, owners, and a recommended next step.

Frequently Asked Questions about decision-doc

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

FAQPage Schema
How do I create a decision log for a build vs buy evaluation?

A product decision log captures the rationale, considered alternatives, trade-offs, owners, and stakeholder input for strategic choices like build vs buy, ensuring future stakeholders understand why choices were made.

What is the best way to document trade-offs and rationale for architecture choices?

The best way to document architecture trade-offs is to record the decision rationale, alternatives considered, and stakeholder input in a structured log, preventing repeated debates and lost context.

How do I gather stakeholder input for a product decision document?

You gather stakeholder input by using grouped, structured questions to collect relevant perspectives, which prevents follow-up ambiguity and ensures alignment on the product decision rationale and trade-offs.

Does this work for resolving competing feature approaches in product management?

Yes, resolving competing feature approaches is a core use case; the decision log captures the rationale, alternatives, and trade-offs to align stakeholders and preserve the product strategy context.

When do I need a formal decision log for product management?

You need a formal decision log when making strategic product choices like selecting a tech stack or comparing feature approaches, ensuring the rationale and trade-offs are preserved for future stakeholder audits.