one-three-one-rule

Generate a 1-3-1 decision framework with problem statement, three option analyses, and recommendation.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/thisismynewfmail-ui/Monika-agent --skill one-three-one-rule-thisismynewfmail-ui
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/thisismynewfmail-ui/Monika-agent/tree/main/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/thisismynewfmail-ui/Monika-agent --skill one-three-one-rule-thisismynewfmail-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a structured decision‑making format that turns ambiguous technical choices into a clear problem statement, three evaluated options, and a concrete recommendation, helping teams reach consensus quickly.

Core Features & Use Cases

  • Problem framing: Captures the core decision in a single sentence.
  • Three option analysis: Delivers distinct alternatives with pros and cons.
  • Actionable recommendation: Supplies a single chosen path, definition of done, and step‑by‑step implementation plan.
  • Use cases: Architecture selection, tool evaluation, migration strategy planning, or any scenario requiring a balanced trade‑off presentation.

Quick Start

Ask Monika for a 1‑3‑1 analysis of the best database solution for our new service.

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 decision framework for technical proposals?

This framework turns ambiguous technical choices into a structured format: one problem statement, three option analyses with pros and cons, and a single actionable recommendation with a definition of done and implementation plan.

How do I compare architecture choices or migration strategies?

To compare architecture choices or migration strategies, frame the core decision in a single sentence, evaluate three distinct alternatives with pros and cons, and output a single chosen path with a step-by-step implementation plan and definition of done.

When do I need a structured trade-off analysis for tool selection?

You need structured trade-off analysis for tool selection when multiple viable approaches require comparison. It captures the core decision, evaluates three options with pros and cons, and supplies a single actionable recommendation to reach team consensus quickly.

Does this decision-making format work for evaluating technical proposals at scale?

This decision-making format works for evaluating technical proposals at any scale where multiple viable approaches need comparison, including architecture selection, tool evaluation, and migration strategy planning, by delivering a balanced trade-off presentation.

How to generate an actionable recommendation from multiple technical options?

To generate an actionable recommendation, evaluate three distinct options with pros and cons against a single problem statement, then select one path and define its implementation plan and definition of done to guide execution.

What are the limitations of using a 1-3-1 options analysis format?

The 1-3-1 options analysis format is limited to evaluating exactly three alternatives, which may constrain scenarios requiring broader exploration or situations where a single actionable recommendation is insufficient for complex, multi-phase technical decisions.