one-three-one-rule

Generate a 1-3-1 decision analysis with options, recommendation, and implementation plan.

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

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

  • Produce a concise Problem statement that frames the decision clearly.
  • Generate exactly three viable Options (A, B, C) with prioritized pros and cons.
  • Deliver a Recommendation with justification, plus a Definition of Done and an Implementation Plan.
  • Provide a lightweight Verification scaffold to ensure the chosen path can be executed and validated.
  • Use cases include architecture choices, tooling selections, and migration strategy debates.

Quick Start

Provide a complete 1-3-1 decision analysis for a given technical prompt, including Problem, Options A–C, Recommendation, Definition of Done, and 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 technical proposals for architecture decisions and trade-off analysis?

Structure technical proposals using a 1-3-1 decision framing format: one clear problem statement, three distinct options with pros and cons, and one concrete recommendation with a definition of done and implementation plan.

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

Evaluating tool selection is best handled by generating exactly three viable options, prioritizing the pros and cons for each, and delivering a justified recommendation alongside a lightweight verification scaffold.

How do I create an implementation plan and definition of done for migration path evaluations?

Create an implementation plan for migration paths by selecting a recommended option from three evaluated choices, then defining explicit verification criteria and a definition of done to ensure the execution path can be validated.

When do I need structured decision framing for refactoring strategies?

You need structured decision framing for refactoring strategies when facing a choice between multiple approaches and requiring a concise problem statement, distinct options, and a concrete recommendation with an implementation plan.

Does collaborative decision-making work for architecture choices without a defined problem statement?

Collaborative decision-making for architecture choices requires a defined problem statement first, followed by three options and a recommendation, to ensure the chosen path can be properly executed and validated.