one-three-one-rule

Frame technical decisions into a problem statement, three options, and a recommendation.

Updated May 2, 2026
One-click install
npx skills add https://github.com/AlvaroBiano/hermes-agent --skill one-three-one-rule-alvarobiano
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/AlvaroBiano/hermes-agent/tree/main/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/AlvaroBiano/hermes-agent --skill one-three-one-rule-alvarobiano

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Three or more viable approaches to a technical decision often lead to analysis paralysis. The 1-3-1 Rule provides a concise framework to frame the problem, compare three distinct options with trade-offs, and land on a concrete recommendation with a plan.

Core Features & Use Cases

  • Framing: Generates a precise Problem sentence that scopes the decision.
  • Option triad: Presents three viable approaches labeled A, B, and C with concise descriptions and pros/cons.
  • Recommendation & plan: Delivers a justified Recommendation along with a concrete Definition of Done and an actionable Implementation Plan.
  • Use cases: Ideal for architecture decisions, tool selections, refactors, migrations, or any multi-path proposal needing a clear path forward.

Quick Start

Provide the decision context and request a 1-3-1 analysis to generate a clear recommendation.

Frequently Asked Questions about one-three-one-rule

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

FAQPage Schema
What is the 1-3-1 rule for technical decision-making?

The 1-3-1 rule is a decision-making framework that produces one problem sentence, three viable options with trade-offs, and a single recommendation. It helps overcome analysis paralysis in architecture decisions, tool selections, and migrations by providing a structured technical proposal.

How do I structure an architecture decision with multiple options?

Structure an architecture decision by framing a single problem sentence, evaluating three distinct options labeled A, B, and C with pros and cons, and delivering a justified recommendation. This framework also includes a Definition of Done and an actionable Implementation Plan for the chosen path.

Can I use this decision framework for refactoring strategies and migrations?

Yes, this decision framework applies to refactoring strategies, migrations, tool selections, and any multi-path technical proposal. It scopes the decision with a problem statement and compares three viable approaches to land on a concrete recommendation with an implementation plan.

What's the best way to compare technical options with trade-offs?

The best way to compare technical options is using a structured decision brief that presents three viable approaches with concise descriptions and explicit pros and cons. This method ensures risk-tradeoffs are evaluated clearly before selecting a recommendation.

When do I need a structured decision brief for tool selection?

You need a structured decision brief for tool selection when facing three or more viable approaches that cause analysis paralysis. It generates a precise problem statement, compares options with trade-offs, and delivers a justified recommendation with a concrete implementation plan.

Why does comparing too many technical options lead to analysis paralysis?

Comparing too many technical options causes analysis paralysis because viable approaches lack structured trade-off evaluation. The 1-3-1 framework solves this by limiting comparisons to three options with pros and cons, forcing a clear recommendation and actionable implementation plan.