Verified:GitHub

one-three-one-rule

Frame complex technical decisions into a 1-3-1 structure with options and a recommendation.

2|Updated Apr 25, 2026

Search Tags:#trade-offs #recommendation #implementation-plan #options-analysis #definition-of-done #decision-framing #1-3-1

Ready to run

npx skills add https://github.com/AlexiosBluffMara/mercury --skill one-three-one-rule-alexiosbluffmara

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/AlexiosBluffMara/mercury/tree/main/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/AlexiosBluffMara/mercury --skill one-three-one-rule-alexiosbluffmara

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured, repeatable format to decompose complex decisions into a clear problem statement, three actionable options with pros and cons, and a recommended path, enabling faster alignment and execution.

Core Features & Use Cases

Three options labeled A, B, and C with concise pros and cons.
A single, defendable recommendation plus a concrete Definition of Done and Implementation Plan.
Use for architecture decisions, tool selection, refactors, migrations, and any scenario demanding clear trade-offs.

Quick Start

Provide a 1-3-1 analysis for a decision scenario, returning one problem statement, three options with pros/cons, a recommendation, DoD, and an implementation plan.

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 frame a technical decision with clear trade-offs and an implementation plan?▼

To frame a technical decision with trade-offs, decompose the scenario into a 1-3-1 proposal: one problem statement, three options with pros and cons, and one recommendation. This structured format includes a Definition of Done and implementation plan to enable faster alignment.

What is the 1-3-1 framework for architecture decisions and tool selection?▼

The 1-3-1 framework for architecture decisions is a structured format that outputs one defined problem statement, three distinct options labeled A, B, and C with concise pros and cons, and a single defendable recommendation to guide tool selection.

How do I structure an options analysis for a software migration or refactor?▼

Structure an options analysis for a software migration by evaluating three actionable options with pros and cons, selecting a recommended path, and defining a concrete Definition of Done and implementation plan to guide the execution.

When do I need a defined problem statement and three options for recommendation framing?▼

You need a defined problem statement and three options for recommendation framing when selecting architectures, tools, refactors, or migrations. This process is required for any multi-option task demanding clear trade-offs and a defendable recommendation.

Does the 1-3-1 rule require specific dependencies for options analysis?▼

The 1-3-1 rule for options analysis requires no specific dependencies or environment setup. It is a repeatable format applicable to any multi-option technical decision requiring clear trade-offs, a recommendation, and an implementation plan.

What is the best way to document a recommendation and Definition of Done for a complex task?▼

The best way to document a recommendation and Definition of Done is to use a concise 1-3-1 proposal. This format pairs a single defendable recommendation with a concrete Definition of Done and an implementation plan for faster execution.