one-three-one-rule

Produce a 1-3-1 decision with problem, options, and recommendation.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge --skill one-three-one-rule-chris-chai-minjae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge/tree/main/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/Chris-Chai-Minjae/hermes-agent-r1-bridge --skill one-three-one-rule-chris-chai-minjae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured decision-making framework for technical proposals and trade-off analysis. When the user faces a choice between multiple approaches (architecture decisions, tool selection, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros/cons, and one concrete recommendation with definition of done and implementation plan.

Core Features & Use Cases

  • Provides a 1-3-1 decision framing: a single Problem, three options labeled A, B, and C with pros and cons, and a recommended path with a Definition of Done and an implementation plan.
  • Useful for architecture decisions, tool selection, migration planning, and any scenario with multiple viable approaches requiring a clear recommendation.
  • Enables stakeholder-ready proposals by delivering a concise, auditable decision artifact.

Quick Start

Provide a 1-3-1 decision for a technical choice requiring a clear recommendation and concrete 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 structure a technical proposal for architecture trade-off analysis?

Structure a technical proposal using the 1-3-1 framework: one clear problem statement, three options (A/B/C) with pros and cons, and one recommendation with an implementation plan. This format delivers a concise, auditable decision artifact for stakeholders.

What is the best way to document tool selection options with pros and cons?

Document tool selection by defining the problem, outlining three distinct options labeled A, B, and C with their respective pros and cons, and providing a single recommended path with a definition of done and implementation plan.

How do I write an implementation plan for a migration path recommendation?

Write an implementation plan by following the 1-3-1 decision format, which requires selecting one recommended course of action from three evaluated options and detailing the definition of done and execution steps for that migration path.

When do I need a structured decision-making framework for refactoring strategies?

You need a structured decision-making framework for refactoring strategies when multiple viable approaches exist and require a clear recommendation. The 1-3-1 format ensures stakeholder-ready proposals by producing an auditable artifact with defined options and implementation steps.

Can I use this 1-3-1 format for any technical decision involving multiple viable approaches?

Yes, the 1-3-1 format applies to any technical decision with multiple viable approaches, including architecture choices, tool selections, refactoring, and migration paths. It formats the problem, three options with pros and cons, and a recommendation into a concise proposal.