one-three-one-rule

Structure technical decisions into three options with pros, cons, and a recommendation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill addresses the complexity of technical decision-making by providing a structured framework for analyzing options and making clear recommendations.

Core Features & Use Cases

  • Structured Decision-Making: Offers a 1-3-1 format for technical proposals and trade-off analysis.
  • Clear Recommendations: Delivers a single problem statement, three distinct options with pros/cons, and a concrete recommendation.
  • Use Case: When faced with multiple technical approaches, such as architecture decisions or tool selection, this skill can help you decide the best course of action.

Quick Start

Request a 1-3-1 analysis for a specific technical decision.

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 technical proposals to compare trade-offs effectively?

To structure technical proposals, use the 1-3-1 rule framework to define one problem statement, analyze three options with pros and cons, and deliver a clear recommendation.

What is the best way to evaluate architecture decisions and tool selection?

Evaluating architecture decisions is best done using a structured decision-making framework that compares three approaches and provides a concrete recommendation based on trade-off analysis.

How do I create a decision-making framework for complex technical options?

Create a decision-making framework by defining the specific problem, outlining three distinct technical options with pros and cons, and selecting one clear recommendation.

Can I use a 1-3-1 format for documenting software engineering recommendations?

Yes, you can use the 1-3-1 format for documenting software engineering recommendations by providing one problem statement, three options with trade-offs, and a single recommendation.

What input is required to generate options analysis for technical trade-offs?

Generating options analysis requires user input detailing the specific technical problem and the options to be analyzed to produce a structured trade-off comparison and recommendation.