one-three-one-rule

Generates structured decision briefs with one problem, three options, and one recommendation.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a technical decision has multiple viable approaches, unstructured answers bury the recommendation and make it hard for stakeholders to compare trade-offs. This Skill enforces a consistent 1-3-1 format so every decision brief is concise, comparable, and actionable. ## Core Features & Use Cases - Structured Decision Briefs: Produces exactly one problem statement, three labeled options with pros and cons, and a single direct recommendation. - Actionable Follow-Through: Adds a Definition of Done and an Implementation Plan with concrete steps, commands, and tools for the recommended option. - Adaptive Revision: Updates the recommendation, success criteria, and plan if the user selects a different option. - Use Case: A user asks "give me options for adding retry logic to our API client" and receives a brief comparing a shared backoff utility, a retry library, and a queue-based approach, ending with a clear pick and an execution plan. ## Quick Start Ask the agent to give you a 1-3-1 for a technical decision you are facing, such as choosing an architecture, tool, or migration strategy.

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 get a structured decision brief with options and trade-offs?▼

Ask for a 1-3-1 response or say "give me options" for your technical decision. The output contains one problem sentence, three options with pros and cons, a single recommendation, and an implementation plan.

What is the 1-3-1 communication rule for decision-making?▼

The 1-3-1 rule is a decision brief format: one problem statement, three viable options with trade-offs, and one recommendation. It also includes a Definition of Done and an Implementation Plan for the recommended path.

When should I use a 1-3-1 decision brief?▼

Use it when a task has multiple viable approaches with meaningful trade-offs, such as architecture, tooling, or migration decisions, or when you need a proposal to forward to stakeholders. Avoid it for simple questions or debugging sessions.

What happens if I pick a different option than the recommendation?▼

The brief is revised to match your selection. The recommendation, Definition of Done, and Implementation Plan all update to align with the option you chose.

When should I not use the 1-3-1 format?▼

Do not use it for simple questions with one obvious answer, debugging sessions, or tasks where the approach is already decided. The format adds overhead that only pays off when genuine trade-offs exist.