one-three-one-rule

Generate a structured 1-3-1 analysis with three options and an implementation plan.

2|1|Updated Jul 14, 2026
One-click install
npx skills add https://github.com/heysuhas/hermes_cli --skill one-three-one-rule-heysuhas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/heysuhas/hermes_cli/tree/main/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/heysuhas/hermes_cli --skill one-three-one-rule-heysuhas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates ambiguity in technical decision-making by forcing a structured, objective analysis of competing approaches, preventing analysis paralysis and poorly justified architectural choices.

Core Features & Use Cases

  • Structured Trade-off Analysis: Forces the evaluation of exactly three distinct options with pros and cons.
  • Actionable Recommendations: Ensures every decision is paired with a concrete Definition of Done and an implementation plan.
  • Use Case: Use this when you need to propose a new database migration strategy or choose between competing API integration libraries to ensure stakeholders understand the trade-offs and the path forward.

Quick Start

Ask the agent to provide a 1-3-1 analysis for your current technical dilemma to receive a structured proposal with three options and a clear recommendation.

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 for architecture trade-off analysis by evaluating exactly three distinct options with comparative pros and cons, paired with a concise problem statement and an actionable implementation plan.

What is the best way to compare three options for a database migration strategy?

The best way to compare options for a database migration strategy is using a structured decision-making framework that forces objective evaluation of trade-offs to prevent analysis paralysis and poorly justified architectural choices.

How do I create an actionable implementation plan for technical decisions?

Create an actionable implementation plan for technical decisions by ensuring every recommendation is paired with a concrete Definition of Done and defined success criteria to guide stakeholders on the path forward.

When do I need a structured framework for choosing between competing API integration libraries?

You need a structured framework for choosing between competing API integration libraries when you must eliminate ambiguity in technical decision-making and ensure stakeholders understand the trade-offs.

Can I use this to prevent analysis paralysis during tooling decisions?

Yes, you can prevent analysis paralysis during tooling decisions by forcing a structured, objective analysis of competing approaches, which eliminates ambiguity and drives clear architectural choices.