one-three-one-rule

Produces a 1-3-1 decision brief with problem statement, options, pros/cons, recommendation, definition of done, and implementation plan for technical trade-offs.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/matlee0409/cronus --skill one-three-one-rule-matlee0409
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/matlee0409/cronus/tree/main/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/matlee0409/cronus --skill one-three-one-rule-matlee0409

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured decision-making for technical proposals and trade-offs. When there are multiple viable approaches (architecture decisions, tool selections, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros and cons, and one concrete recommendation with a definition of done and an implementation plan.

Core Features & Use Cases

  • Problem framing: distills complex decisions into a precise, testable problem statement.
  • Options with trade-offs: provides three distinct approaches with pros, cons, and risk considerations.
  • Recommendation and plan: outputs a clear recommended path plus a DoD and an actionable implementation plan.
  • Reusability: suitable for architecture decisions, tooling choices, refactors, migrations, or process changes.

Quick Start

Ask for a 1-3-1 decision analysis when you need a clear problem, three options with pros and cons, and a recommended plan.

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 format for technical decision-making?▼

The 1-3-1 format structures technical decisions into one clear problem statement, three distinct options with pros and cons, and one concrete recommendation with a definition of done and implementation plan.

How do I structure architecture trade-off analysis for multiple viable approaches?▼

Structure architecture trade-off analysis by framing a testable problem statement, evaluating three options with risk considerations, and selecting a recommended path with a definition of done and actionable implementation plan.

When do I need a structured decision brief for migration paths?▼

You need a structured decision brief for migration paths when multiple viable approaches exist and you require a clear problem statement, three options with trade-offs, and a concrete recommendation with an implementation plan.

Can I use this 1-3-1 method for tool selection and refactoring strategies?▼

Yes, the 1-3-1 method applies to tool selections and refactoring strategies by distilling complex decisions into a problem statement, three options with pros and cons, and a recommended plan with a definition of done.

How to create an actionable implementation plan from technical proposal options?▼

Create an actionable implementation plan by evaluating three distinct options with trade-offs, selecting one concrete recommendation, and defining the done criteria and implementation steps as part of the recommended path.

What is the best way to document risk assessment for architecture decisions?▼

Document risk assessment for architecture decisions by providing three distinct approaches with pros, cons, and risk considerations, followed by a clear recommended path with a definition of done and implementation plan.