skills.rest
xu1713
xu1713COMMUNITY
Explore all skills by this author →
GitHub

one-three-one-rule

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

Updated Jun 5, 2026
Search Tags:#communication#recommendation#decision-making#trade-off analysis#architecture decision#1-3-1#technical proposal
One-click install
npx skills add https://github.com/xu1713/openhorse --skill one-three-one-rule-xu1713
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/xu1713/openhorse/tree/main/openhorse/openhorse/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/xu1713/openhorse --skill one-three-one-rule-xu1713

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 a defensible recommendation. This Skill structures the analysis into a consistent 1-3-1 format so stakeholders can compare options and act on a concrete plan. ## Core Features & Use Cases - Structured Decision Format: Produces one problem statement, three distinct options (A, B, C) with pros and cons, and one direct recommendation. - Actionable Output: Includes a Definition of Done with verifiable success criteria and a step-by-step implementation plan for the recommended option. - Adaptive Revision: If the user selects a different option, the recommendation, Definition of Done, and implementation plan update accordingly. - Use Case: When deciding how to add retry logic to an API client, get a comparison of a shared backoff utility, a retry library, and a queue-based approach, with a clear recommendation and execution steps. ## Quick Start Ask the agent to give you a 1-3-1 for your technical decision, such as choosing between architecture or tooling approaches.

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 three distinct options with pros and cons, then give one recommendation with a definition of done and implementation plan. This keeps trade-off analysis concise and actionable.

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

The 1-3-1 rule is a communication framework with one problem statement, three viable options with trade-offs, and one concrete recommendation. It forces clarity by limiting scope and requiring a direct professional judgment.

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

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

What are the limitations of the 1-3-1 decision format?▼

The format requires exactly three genuinely distinct options, which can feel forced when only two real choices exist. It also assumes the decision-maker wants a single recommendation rather than an open-ended exploration.

How does the recommendation change if I pick a different option?▼

If you select a different option than the recommended one, the recommendation, definition of done, and implementation plan are revised to match your choice. The success criteria and steps always align with the selected path.

Related Skills

Explore More Content & Communication Skills→
faizkhairifaizkhairi
64

elicit-requirements

Gather structured pre-feature requirements including acceptance criteria and technical constraints.

Community
Intermediate
tailcallhqtailcallhq
7.5k

execute-plan

Execute structured task plans with status tracking and progress updates.

Official
Intermediate
hotriluanhotriluan

ck:brainstorm

Brainstorm software architecture options with trade-off analysis and recommendations.

Community
Advanced
viditparashar96viditparashar96

eng-architecture-decision

Create Architecture Decision Records with weighted comparison matrices and risk mitigations.

Community
Advanced