one-three-one-rule

Creates a structured 1-3-1 decision analysis with problem statement, options, pros/cons, recommendation, definition of done, and implementation plan.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Structured decision-making framework for technical proposals and trade-off analysis. When the user faces a choice between multiple approaches (architecture decisions, tool selection, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros/cons, and one concrete recommendation with definition of done and implementation plan. Use when the user asks for a "1-3-1", says "give me options", or needs help choosing between competing approaches.

Core Features & Use Cases

  • Structured decision-making format for when a task has multiple viable approaches and the user needs a clear recommendation. Produces a concise problem framing, three options with trade-offs, and an actionable plan for the recommended path.
  • Use when the user explicitly asks for a "1-3-1" response.
  • This framework helps teams quickly align on a recommended path and a concrete implementation plan.

Quick Start

Provide a complete 1-3-1 decision analysis for a given technical choice.

Frequently Asked Questions about one-three-one-rule

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a 1-3-1 framework for technical decision-making?

The 1-3-1 framework is a structured decision-making format for technical proposals that produces one problem statement, three options with trade-offs, and one concrete recommendation with an implementation plan.

How do I compare multiple architecture approaches during a tool selection?

Comparing multiple architecture approaches is done by generating three distinct options with pros and cons, then selecting one recommended choice accompanied by a definition of done and a concrete implementation plan.

How do I structure trade-off analysis for refactoring strategies or migration paths?

Structuring trade-off analysis for refactoring strategies or migration paths requires framing a clear problem statement, evaluating three viable options with pros and cons, and finalizing one actionable recommendation.

When do I need a structured options analysis format for technical proposals?

You need a structured options analysis format for technical proposals when a task has multiple viable approaches and your team requires a clear recommendation and a concrete implementation plan to align quickly.

Can I use this options analysis framework for non-technical business decisions?

This options analysis framework is designed for technical projects like architecture decisions, tool selection, refactoring strategies, and migration paths, enforcing a fixed output structure for technical trade-off evaluation.

What does a 1-3-1 decision analysis output include for an implementation plan?

A 1-3-1 decision analysis output includes a problem statement, three options with pros and cons, a recommended choice, a definition of done, and an implementation plan to guide the technical project.