one-three-one-rule

Structure technical decisions into one problem, three options, and one recommendation.

3|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill one-three-one-rule-twjarviszyra-web
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/twjarviszyra-web/hermes-unbound/tree/main/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/twjarviszyra-web/hermes-unbound --skill one-three-one-rule-twjarviszyra-web

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you make and communicate difficult technical decisions when there are multiple viable approaches and stakeholders need a concise, defensible recommendation.

Core Features & Use Cases

  • Problem Framing: Reduces a complex choice to one clear decision statement.
  • Three Viable Options: Compares distinct approaches with practical pros and cons.
  • Actionable Recommendation: Ends with a recommended path, definition of done, and implementation plan.
  • Use Case: Use it for architecture decisions, tooling selection, refactoring plans, migration strategies, and team proposals.

Quick Start

Ask for a 1-3-1 analysis of your decision and include the competing options plus any constraints you want weighed.

Frequently Asked Questions about one-three-one-rule

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

FAQPage Schema
How do I structure an architecture decision proposal with multiple viable options?

Structure your architecture decision proposal using the 1-3-1 rule: define one problem statement, compare three viable options with pros and cons, and conclude with one recommendation that includes a definition of done and an implementation plan.

What is the best way to compare trade-offs for a system migration strategy?

The best way to compare migration trade-offs is to frame the strategy as a 1-3-1 proposal, evaluating exactly three distinct approaches with practical pros and cons before selecting a recommended path with a clear implementation plan.

How do I write a technical recommendation for refactoring when stakeholders need a concise summary?

Write a technical recommendation by reducing the refactoring choice to one clear decision statement, weighing three options with trade-offs, and delivering one actionable recommendation with a definition of done and implementation plan.

Can I use this 1-3-1 proposal method for tool selection and framework comparisons?

Yes, you can use the 1-3-1 proposal method for tool selection and framework comparisons by providing the competing options and any constraints you want weighed to receive a structured analysis with three options and a final recommendation.

When do I need a formal decision-making structure for technical trade-offs?

You need a formal decision-making structure for technical trade-offs when multiple viable paths exist for architecture choices or migrations and stakeholders require a concise, defensible recommendation with an implementation plan.