decision-making

Apply a 1-3-1 framework to identify problems, propose options, and recommend decisions.

3|Updated Jan 22, 2026
One-click install
npx skills add https://github.com/falconnt/windsurf-skills --skill decision-making
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: decision-making
Source: https://github.com/falconnt/windsurf-skills/tree/main/decision-making
Command: npx skills add https://github.com/falconnt/windsurf-skills --skill decision-making

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams avoid analysis paralysis by providing a repeatable structure to frame significant decisions, define a core problem, generate three distinct options, evaluate trade-offs, and converge on a clear recommendation.

Core Features & Use Cases

  • Structured decision framework: Identify core problem, generate three viable options with trade-offs, and provide a single recommendation.
  • Use cases: Selecting architectures, tools, or design approaches across projects.
  • Quick scenario: When faced with choosing between implementation approaches, this Skill yields a robust, auditable decision path.

Quick Start

Invoke with @decision-making to structure a significant decision: provide the Core Problem, 3 Options (with pros/cons), and one Recommendation.

Frequently Asked Questions about decision-making

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

FAQPage Schema
How do I structure architecture trade-off decisions to avoid analysis paralysis?

To structure architecture trade-off decisions, apply a 1-3-1 framework: identify the core problem, generate three viable options with pros and cons, and converge on a single recommendation.

What is the 1-3-1 framework for making technical tool selection decisions?

The 1-3-1 framework for tool selection enforces a three-step process: define one core problem, propose three distinct options with evaluated trade-offs, and select one final recommendation.

How do I evaluate design trade-offs across multiple implementation approaches?

You evaluate design trade-offs by generating three distinct viable options, comparing their specific pros and cons, and converging on a single robust recommendation.

Can I use a structured decision framework for high-stakes architecture choices?

Yes, you can use a structured decision framework for high-stakes architecture choices by defining the core problem, evaluating three options, and providing a single auditable recommendation.

What's the best way to document a robust decision path for design approaches?

The best way to document a robust decision path is applying a 1-3-1 structure: state the core problem, list three options with trade-offs, and conclude with one recommendation.

When should I avoid using a structured framework for technical decisions?

You should avoid using a structured framework for technical decisions when the problem scope is trivial, lacks distinct viable options, or requires immediate action without generating three alternatives.