one-three-one-rule

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

Updated May 20, 2026
One-click install
npx skills add https://github.com/SriRamkunamsetty/SITA2.0-HermesAgent --skill one-three-one-rule-sriramkunamsetty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/SriRamkunamsetty/SITA2.0-HermesAgent/tree/main/hermes-agent/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/SriRamkunamsetty/SITA2.0-HermesAgent --skill one-three-one-rule-sriramkunamsetty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured decision-making framework that reduces ambiguity by forcing a clear problem statement, explicit options, and a single, actionable recommendation.

Core Features & Use Cases

  • Three clearly labeled options (A, B, C) with pros and cons.
  • One definitive recommendation with a defined Definition of Done and an implementation plan.
  • Use cases include architecture decisions, tool selections, refactoring strategies, and migration planning.

Quick Start

Provide a 1-3-1 decision brief for selecting between competing architectural approaches.

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 framework for architecture decisions?

The 1-3-1 framework is a structured decision-making format that captures one clear problem statement, three labeled options with pros and cons, and a single recommendation with an implementation plan. It reduces ambiguity during architecture reviews and tool selection.

How do I write an options analysis brief for migration planning?

Write an options analysis brief by defining a crisp problem statement, evaluating three options labeled A, B, and C with explicit trade-offs, and selecting one recommendation. Conclude the brief with a Definition of Done and an actionable implementation plan.

When do I need a structured proposal for tool selection?

You need a structured proposal for tool selection when choosing between competing architectural approaches or refactoring strategies. It enforces a fixed structure to compare trade-offs and delivers a decision-ready output with a definitive recommendation and implementation plan.

Can I use this decision-making format for refactoring strategies?

Yes, you can use this decision-making format for refactoring strategies. It captures the problem, maps three options with trade-offs, and outputs a single recommendation with a Definition of Done and an implementation plan, enabling fast decision-ready outputs for technical projects.

What is the best way to present trade-offs for competing architectural approaches?

The best way to present trade-offs is using a fixed 1-3-1 structure. Formulate one problem statement, document three options labeled A, B, and C with explicit pros and cons, and conclude with a recommended option, a Definition of Done, and an implementation plan.