one-three-one-rule

Structure technical decisions into one problem, three options, and one recommendation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill helps users make technical decisions by providing a clear and structured 1-3-1 format: one problem statement, three options with pros/cons, and one recommended solution with a definition of done and implementation plan.

Core Features & Use Cases

  • Structured Decision-Making: Offers a standardized approach to evaluating and choosing between multiple technical options.
  • 1-3-1 Format: Provides a clear and concise format for problem statements, options, and recommendations.
  • Use Case: When a user is considering different architectures, tool selections, or refactoring strategies and needs a well-defined recommendation.

Quick Start

Ask the AI to provide a 1-3-1 decision for choosing a database technology based on your specific requirements.

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 format for technical decision-making?

The 1-3-1 format is a structured decision-making method that defines one problem statement, evaluates three distinct options with pros and cons, and delivers one specific recommendation with an implementation plan.

How do I structure a technical proposal for choosing between multiple architectures?

Structure a technical proposal by defining one problem statement, analyzing three viable options with their trade-offs, and providing one recommended solution with a definition of done and implementation plan.

When should I use a structured trade-off analysis for software engineering decisions?

Use structured trade-off analysis when considering different architectures, tool selections, or refactoring strategies and you need a well-defined recommendation among multiple viable technical approaches.

Can I use this structured analysis for database technology selection?

Yes, you can use this structured analysis for database technology selection by asking the AI to provide a 1-3-1 decision based on your specific requirements and evaluating the trade-offs.

What does a 1-3-1 technical proposal recommendation include?

A 1-3-1 technical proposal recommendation includes a specific solution choice, a defined outcome, and a clear implementation plan to guide the execution of the selected technical approach.

Are there limitations to using the 1-3-1 format for trade-off analysis?

The 1-3-1 format limits analysis to exactly three options, which may not capture the full complexity of trade-offs in decisions requiring evaluation of more diverse technical alternatives.