one-three-one-rule

Generate a 1-3-1 decision brief with options, pros, cons, and recommendation.

150|25|Updated Apr 20, 2026
One-click install
npx skills add https://github.com/Devsoul2026/Hermes-One-Click --skill one-three-one-rule-devsoul2026
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/Devsoul2026/Hermes-One-Click/tree/main/hermes-agent/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/Devsoul2026/Hermes-One-Click --skill one-three-one-rule-devsoul2026

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams decide between multiple technical approaches by generating a clear 1-3-1 decision brief that frames the problem, outlines three distinct options with pros and cons, and delivers a concrete recommendation with a definition of done and an implementation plan.

Core Features & Use Cases

  • Produces a single Problem statement
  • Presents exactly three options labeled A, B, and C with pros and cons
  • Delivers a clear, justified Recommendation and a concrete Definition of Done
  • Includes an actionable Implementation Plan and defined success criteria
  • Uses in architecture decisions, tooling selections, migrations, or major refactors with stakeholder buy-in

Quick Start

Draft a concise 1-3-1 decision brief for selecting a frontend framework.

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 brief and when should I use it for architecture decisions?

A 1-3-1 decision brief is a structured format for options analysis that frames one problem statement, three distinct choices with pros and cons, and one recommendation. Use it for architecture decisions, tooling selections, or migrations requiring stakeholder alignment.

How do I draft a structured decision-making brief for selecting a frontend framework?

Draft a decision-making brief by defining the problem scope, presenting three options labeled A, B, and C with pros and cons, and delivering a justified recommendation with a definition of done and an implementation plan for stakeholder review.

Can I use the 1-3-1 framework for major refactors needing stakeholder buy-in?

Yes, the 1-3-1 framework suits major refactors by providing a repeatable template that outlines three approaches with trade-offs and a concrete recommendation, ensuring stakeholders clearly understand the implementation plan and success criteria.

What's the best way to present technical options analysis to stakeholders?

The best way to present options analysis is a 1-3-1 brief that clearly defines scope, inputs, and expected outcomes, then contrasts three approaches with pros and cons before delivering a defendable recommendation with an actionable implementation plan.

Does a 1-3-1 decision brief include success criteria and an implementation plan?

Yes, a 1-3-1 decision brief includes defined success criteria, a concrete definition of done, and an actionable implementation plan alongside the problem statement, three options, and final recommendation to guide technical execution.