one-three-one-rule

Evaluate technical proposals by comparing three options and generating an implementation roadmap.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves ambiguity in technical decision-making by forcing a structured, objective evaluation of competing strategies, preventing analysis paralysis and ensuring clear communication with stakeholders.

Core Features & Use Cases

  • Structured Framing: Converts complex technical trade-offs into a standardized 1-3-1 format (1 problem, 3 options, 1 recommendation).
  • Actionable Planning: Automatically generates a Definition of Done and an implementation roadmap for the chosen path.
  • Use Case: When a team is debating between three different database migration strategies, use this skill to objectively compare the pros and cons of each and receive a concrete, step-by-step execution plan.

Quick Start

Ask the agent to provide a 1-3-1 analysis for your specific technical dilemma to receive a structured proposal and implementation plan.

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 for architecture design and tool selection?

Structure technical proposals using the 1-3-1 framework: define 1 problem, compare 3 distinct options, and provide 1 actionable recommendation. This standardizes trade-off evaluation and resolves decision-making ambiguity for stakeholders.

What is the best way to compare trade-offs for a database migration strategy?

The best way to compare migration strategy trade-offs is applying a structured 1-3-1 analysis. This objectively frames the problem, contrasts three viable approaches, and yields a concrete, step-by-step execution plan.

How do I prevent analysis paralysis when debating multiple viable technical approaches?

Prevent analysis paralysis by forcing a structured evaluation of competing strategies into a 1-3-1 format. This objective framework ensures clear problem framing, comparative analysis, and actionable implementation planning.

Can I automatically generate an implementation roadmap after choosing a technical direction?

Yes, after choosing a technical direction, the framework automatically generates a Definition of Done and an implementation roadmap. This provides actionable planning for the selected architecture or migration path.

When do I need a structured decision-making framework for technical trade-offs?

You need a structured decision-making framework when multiple viable technical approaches exist for tasks like architecture design, tool selection, or migration strategy. It ensures objective evaluation and clear communication with stakeholders.