one-three-one-rule

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

539|39|Updated May 1, 2026
One-click install
npx skills add https://github.com/Tommy-yw/RunbookHermes --skill one-three-one-rule-tommy-yw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/Tommy-yw/RunbookHermes/tree/main/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/Tommy-yw/RunbookHermes --skill one-three-one-rule-tommy-yw

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The Skill assists users in making complex technical decisions by providing a structured 1-3-1 framework: one clear problem statement, three distinct options, and one concrete recommendation.

Core Features & Use Cases

  • Structured Decision-Making: Offers a clear and concise format for proposing technical solutions.
  • Trade-Off Analysis: Provides a comprehensive overview of the pros and cons for each option.
  • Recommendation with Implementation Plan: Ensures that the user has a clear path forward with actionable steps.

Quick Start

Ask for a 1-3-1 decision for selecting a database system for your project.

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

The 1-3-1 framework is a structured format for technical proposals that defines one clear problem statement, three distinct options with trade-off analysis, and one concrete recommendation with an implementation plan.

How do I write a technical proposal for system architecture trade-offs?

To write a technical proposal for system architecture trade-offs, frame a clear problem statement, compare three viable approaches by evaluating their pros and cons, and conclude with a single recommendation supported by an actionable implementation plan.

Can I use this structured decision-making format for database selection and refactoring strategies?

Yes, you can apply this structured decision-making format to scenarios involving multiple viable approaches, including database selection, architecture decisions, and refactoring strategies by generating a comprehensive trade-off analysis document.

What is the best way to compare multiple viable approaches for a technical solution?

The best way to compare multiple viable approaches is using a structured trade-off analysis that contrasts three distinct options against a single problem statement to produce a clear recommendation with an implementation plan.

When should I not use a 1-3-1 format for technical proposals?

You should not use the 1-3-1 format for technical proposals when your problem lacks multiple viable approaches or when the scenario does not require detailed trade-off analysis, option comparison, and a recommendation with an implementation plan.