skills.rest
liumeixin
liumeixinCOMMUNITY
Explore all skills by this author →
GitHub

one-three-one-rule

Generate 1-3-1 format recommendations for technical proposals with implementation plans.

4|Updated May 14, 2026
Search Tags:#trade-offs#recommendation#decision-making#technical proposal#1-3-1 format
One-click install
npx skills add https://github.com/liumeixin/hermes-skills --skill one-three-one-rule-liumeixin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/liumeixin/hermes-skills/tree/main/communication/one-three-one-rule
Command: npx skills add https://github.com/liumeixin/hermes-skills --skill one-three-one-rule-liumeixin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When facing multiple viable approaches in technical decision-making, this Skill assists in creating a 1-3-1 format for problem statement, options with pros/cons, and a concrete recommendation with implementation plan.

Core Features & Use Cases

  • 1-3-1 Decision Format: Generates a structured recommendation format for technical decisions.
  • Option Comparison: Evaluates and presents three distinct options with pros and cons.
  • Recommendation & Implementation: Provides a recommended approach with clear implementation guidelines.

Quick Start

Activate the 'one-three-one-rule' Skill and present your problem, followed by the desired decision format (e.g., "1-3-1 for selecting the best database system for our new application").

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 structures technical proposals by defining one problem statement, evaluating three distinct approaches with pros and cons, and delivering one concrete recommendation with an implementation plan.

How do I structure a technical proposal with multiple viable approaches?▼

To structure a technical proposal with multiple approaches, define the problem, compare three options with trade-offs, and conclude with a recommended approach featuring clear implementation guidelines.

When do I need a structured format for evaluating software architecture trade-offs?▼

A structured format is needed for evaluating software architecture trade-offs when decision-makers require a clear framework to compare multiple viable approaches and outline an implementation plan.

How to evaluate and compare technical options with pros and cons?▼

Evaluating technical options requires comparing three distinct approaches, weighing their respective pros and cons, and synthesizing the trade-offs into a single recommended implementation path.

Can I use the 1-3-1 format for selecting systems like a database for my application?▼

Yes, you can use the 1-3-1 format for selecting a database system by presenting your problem to generate three compared options and a final recommendation with implementation guidelines.

Related Skills

Explore More Software Engineering Skills→
Quill-AgentQuill-Agent
3

one-three-one-rule

Generate a 1-3-1 format for technical proposal and trade-off analysis.

Community
Intermediate
AmidVoshakulAmidVoshakul

architecture-decision-records

Standardize creation and maintenance of Architecture Decision Records with templates.

Community
Intermediate
microwindmicrowind
65

algorithm-advisor

Analyze algorithm options and estimate complexity for constrained system designs.

Official
Advanced
yunseo-kimyunseo-kim
1

decision-helper

Apply analytical frameworks like SWOT and Decision Matrix to evaluate options.

Community
Basic