one-three-one-rule

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

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

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. Use when the user asks for a "1-3-1", says "give me options", or needs help choosing between competing approaches.

Core Features & Use Cases

  • Provides a one-sentence Problem, three Option blocks A/B/C with Pros/Cons, a Recommendation, DoD and Implementation Plan.
  • Facilitates structured decision-making in architectural, tooling, and migration scenarios.
  • Ensures outputs are verifiable and repeatable.

Quick Start

Ask the assistant to generate a 1-3-1 decision analysis for a defined technical choice.

Frequently Asked Questions about one-three-one-rule

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a 1-3-1 decision analysis format for technical proposals?

A 1-3-1 decision analysis framework structures a technical proposal by defining one problem statement, three options with pros and cons, and one concrete recommendation to guide competing approach selection.

How do I structure an architecture decision between multiple migration paths?

Structure architecture decision analysis by stating a single problem, detailing three options A/B/C with pros and cons, and delivering a recommendation with a definition of done and implementation plan.

When should I use a 1-3-1 framework for tool selection and refactoring strategies?

Use a 1-3-1 framework for tool selection and refactoring strategies when you need structured decision-making to compare multiple technical approaches and require a verifiable, repeatable output format.

What is the best way to present technical trade-off analysis for a software migration?

The best way to present technical trade-off analysis is a 1-3-1 format: one problem statement, three option blocks with pros and cons, and one recommendation paired with a definition of done.

Can I use this 1-3-1 format to compare refactoring strategies and architecture decisions?

Yes, you can use the 1-3-1 format to compare refactoring strategies and architecture decisions by generating three option blocks with pros and cons and delivering a concrete recommendation with an implementation plan.