one-three-one-rule

Generates structured 1-3-1 decision proposals with three options and one recommendation.

14|5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill one-three-one-rule-mlt-oss
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/MLT-OSS/hermes-agent-go/tree/main/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/MLT-OSS/hermes-agent-go --skill one-three-one-rule-mlt-oss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When facing technical decisions with multiple viable approaches, it is hard to present trade-offs clearly and reach an actionable conclusion. This Skill structures the analysis into a consistent 1-3-1 format so stakeholders get one problem statement, three compared options, and a concrete recommendation. ## Core Features & Use Cases - Structured Decision Format: Produces one problem statement, exactly three options (A, B, C) with pros and cons, and one direct recommendation. - Actionable Follow-Through: Adds a Definition of Done and an Implementation Plan with concrete steps, commands, and tools for the recommended option. - Use Case: When asked to choose between retry strategies for an API client, the Skill compares a shared backoff utility, a retry library, and a queue-based approach, then recommends one with verifiable success criteria and an implementation plan. ## Quick Start Ask the agent to give you a 1-3-1 for choosing between approaches to your technical decision, such as adding retry logic to an API client.

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 a technical proposal with multiple options?

Use the 1-3-1 format: state one problem sentence, present exactly three distinct options with pros and cons each, then give one recommendation with a definition of done and an implementation plan. This keeps proposals concise and forwardable to stakeholders.

What is the 1-3-1 rule for decision making?

The 1-3-1 rule is a communication framework with one problem statement, three options with trade-offs, and one recommendation. It forces clear problem framing and a direct professional judgment instead of hedging between alternatives.

When should I use a 1-3-1 proposal instead of a direct answer?

Use it when a task has multiple viable approaches with meaningful trade-offs, such as architecture, tooling, or migration decisions. Do not use it for simple questions with one obvious answer, debugging sessions, or when the approach is already decided.

How many options should a decision proposal include?

This framework requires exactly three options labeled A, B, and C. The options must represent genuinely different strategies with distinct pros and cons, not minor variations of the same approach.

What happens if the user picks a different option than recommended?

The Definition of Done and Implementation Plan are revised to match the option the user selects. The recommendation section reflects professional judgment, but the actionable sections always align with the chosen path.