skills.rest
matthew-johnson
matthew-johnsonCOMMUNITY
Explore all skills by this author →
GitHub

one-three-one-rule

Generate a 1-3-1 decision brief with one problem, three options, and a recommendation.

Updated Apr 20, 2026
Search Tags:#architecture#framework#recommendation#decision-making#stakeholders#options-analysis
One-click install
npx skills add https://github.com/matthew-johnson/hermes-agent --skill one-three-one-rule-matthew-johnson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: one-three-one-rule
Source: https://github.com/matthew-johnson/hermes-agent/tree/main/optional-skills/communication/one-three-one-rule
Command: npx skills add https://github.com/matthew-johnson/hermes-agent --skill one-three-one-rule-matthew-johnson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Facilitates clear, structured decision-making for technical proposals by converting ambiguity into a concise brief that highlights a problem statement, options, and recommended actions.

Core Features & Use Cases

  • Produces a 1-3-1 decision format: one problem statement, three distinct options with pros and cons, and a single recommended path with a definition of done and an implementation plan.
  • Useful for architecture decisions, tool selections, refactoring strategies, and migration paths where teams need a clear path forward and stakeholder alignment.
  • Supports consistent communications with teams and stakeholders by standardizing decision briefs and acceptance criteria.

Quick Start

Provide a 1-3-1 decision brief for your next technical proposal.

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 format an architecture decision brief for stakeholders?▼

Structure technical trade-off decisions by presenting one problem sentence, three options labeled A, B, and C with pros and cons, and a single recommendation with a definition of done and implementation plan.

What is the best way to present technical options analysis for a tool selection?▼

The best way to present options analysis is the 1-3-1 format: one problem statement, three options with pros and cons, and one recommendation with a definition of done and implementation plan.

How do I create a structured recommendation for a migration path?▼

To create a structured recommendation for a migration path, define a single problem sentence, outline three options with pros and cons, and provide one recommendation with a definition of done and implementation plan.

Can I use a 1-3-1 format for refactoring strategy decisions?▼

Yes, the 1-3-1 format applies to refactoring strategies by delivering three explicit options with pros and cons and a single recommendation with a definition of done and implementation plan.

When do I need a structured decision-making framework for technical proposals?▼

You need a structured decision-making framework when converting ambiguous technical proposals into concise briefs that highlight a problem statement, three options, and a recommended action for stakeholder alignment.

Related Skills

Explore More Content & Communication Skills→
Quill-AgentQuill-Agent
3

one-three-one-rule

Generate a 1-3-1 format for technical proposal and trade-off analysis.

Community
Intermediate
jason660519jason660519

one-three-one-rule

Organize complex decisions into one problem, three options, and one recommendation.

Community
Intermediate
ilanf23ilanf23
1

stakeholder-alignment

Create stakeholder maps, RACI matrices, decision frameworks, and communication plans.

Community
Basic
ldzhhxxldzhhxx
1

one-three-one-rule

Structure technical decisions into one problem, three options, and one recommendation.

Community
Intermediate