one-three-one-rule

Generate three technical options with pros, cons, and a recommended plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured decision-making framework for when a user faces multiple approaches (architecture decisions, tool choices, refactoring strategies, migration paths). The skill produces a clear 1-3-1 format: one concise problem statement, three distinct options with pros and cons, and a concrete recommendation with a definition of done and an implementation plan.

Core Features & Use Cases

  • Generates exactly three options labeled A, B, and C, each with a concise description, pros, and cons.
  • Provides a single, well-justified recommendation based on user context and priorities.
  • Includes a concrete Definition of Done and a practical Implementation Plan to operationalize the recommended option.
  • Useful for evaluating architectural decisions, tool selections, or migration paths in technical projects.

Quick Start

Provide a 1-3-1 analysis: state the problem, present three distinct options with pros and cons, give a final recommendation with a definition of done and an 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 to compare architecture options?

To structure technical proposals, define one problem statement, present three options with pros and cons, and give a recommendation with an implementation plan. This clarifies trade-offs for architecture decisions.

What is the best way to present trade-offs when evaluating migration paths?

The best way to present migration trade-offs is generating three distinct options labeled A, B, and C, each with concise pros and cons, followed by a single recommended path with a definition of done.

Can I use a 1-3-1 format for tool selection and refactoring strategies?

Yes, you can use the 1-3-1 format for tool selection and refactoring strategies. It provides a structured decision-making framework that delivers three options with trade-offs and a concrete recommendation.

How do I create a recommendation and implementation plan for architecture decisions?

Create a recommendation for architecture decisions by selecting one of three presented options, then define a concrete Definition of Done and a practical Implementation Plan to operationalize the chosen path.

Does this decision-making framework always require exactly three options?

Yes, the decision-making framework requires exactly three distinct options labeled A, B, and C. Each option must include a concise description, pros, and cons before delivering a single recommendation.