Skip to content

feat(skills): add one-three-one-rule communication skill#1262

Closed
Willardgmoore wants to merge 2 commits into
NousResearch:mainfrom
Willardgmoore:feat/one-three-one-rule-skill
Closed

feat(skills): add one-three-one-rule communication skill#1262
Willardgmoore wants to merge 2 commits into
NousResearch:mainfrom
Willardgmoore:feat/one-three-one-rule-skill

Conversation

@Willardgmoore

Copy link
Copy Markdown
Contributor

Enforces the 1-3-1 communication framework for clear, structured agent responses: a single-sentence Problem, exactly three Options (with pros/cons), a clear Recommendation, Definition of Done, and Implementation Plan aligned to the chosen option. When the user picks a different option, the skill instructs the agent to revise Recommendation, DoD, and Implementation Plan accordingly. No env vars or external deps; useful whenever a task needs a structured problem/options/recommendation flow.

What does this PR do?

Adds a one-three-one-rule communication skill that enforces a 1-3-1 response format: a single-sentence Problem, exactly three Options (with pros/cons), a Recommendation, Definition of Done, and Implementation Plan aligned to the chosen option. When the user asks for a “1-3-1” or a task needs a structured problem/options/recommendation flow, the agent loads this skill and follows the format; if the user picks a different option, the skill instructs the agent to revise Recommendation, DoD, and Implementation Plan accordingly. Implemented as a skill (instructions only, no code changes) so it’s optional and easy to extend.

Related Issue

Fixes # N/A — no issue.

Type of Change

  • 🐛 Bug fix (non-breaking change that fixes an issue)
  • ✨ New feature (non-breaking change that adds functionality)
  • 🔒 Security fix
  • 📝 Documentation update
  • ✅ Tests (adding or improving test coverage)
  • ♻️ Refactor (no behavior change)
  • 🎯 New skill (bundled or hub)

Changes Made

  • skills/communication/one-three-one-rule/SKILL.md — new skill (frontmatter + 1-3-1 protocol, rules, example)

How to Test

  1. From repo root: hermes chat (or hermes --toolsets skills if you use that).
  2. Ask for a 1-3-1, e.g.: “Give me a 1-3-1 for how we should add retry logic to the API client.”
  3. Confirm the reply has: one-sentence Problem, three Options (A/B/C with pros/cons), Recommendation, Definition of Done, and Implementation Plan for the recommended option.

Checklist

Code

  • I've read the Contributing Guide
  • My commit messages follow Conventional Commits (fix(scope):, feat(scope):, etc.)
  • I searched for existing PRs to make sure this isn't a duplicate
  • My PR contains only changes related to this fix/feature (no unrelated commits)
  • I've run pytest tests/ -q and all tests pass
  • I've added tests for my changes (required for bug fixes, strongly encouraged for features)
  • I've tested on my platform:

Documentation & Housekeeping

  • I've updated relevant documentation (README, docs/, docstrings) — or N/A
  • I've updated cli-config.yaml.example if I added/changed config keys — or N/A
  • I've updated CONTRIBUTING.md or AGENTS.md if I changed architecture or workflows — or N/A
  • I've considered cross-platform impact (Windows, macOS) per the compatibility guide — or N/A
  • I've updated tool descriptions/schemas if I changed tool behavior — or N/A

For New Skills

  • This skill is broadly useful to most users (if bundled) — see Contributing Guide
  • SKILL.md follows the standard format (frontmatter, trigger conditions, steps, pitfalls)
  • No external dependencies that aren't already available (prefer stdlib, curl, existing Hermes tools)
  • I've tested the skill end-to-end: hermes chat then e.g. “Give me a 1-3-1 for integrating with Linear” and verified the 1-3-1 structure in the response

Screenshots / Logs

Screenshot 2026-03-14 at 12 47 50 AM

Enforces the 1-3-1 communication framework for clear, structured agent
responses: a single-sentence Problem, exactly three Options (with pros/cons),
a clear Recommendation, Definition of Done, and Implementation Plan aligned
to the chosen option. When the user picks a different option, the skill
instructs the agent to revise Recommendation, DoD, and Implementation Plan
accordingly. No env vars or external deps; useful whenever a task needs a
structured problem/options/recommendation flow.
teknium1 pushed a commit that referenced this pull request Mar 29, 2026
Adds a structured 1-3-1 decision-making framework as an optional skill.
Produces: one problem statement, three options with trade-offs, one
recommendation with definition of done and implementation plan.

Moved to optional-skills/ (niche communication framework, not broadly
needed by default). Improved description with clearer trigger conditions
and replaced implementation-specific example with a generic one.

Based on PR #1262 by Willardgmoore.
teknium1 added a commit that referenced this pull request Mar 29, 2026
Adds a structured 1-3-1 decision-making framework as an optional skill.
Produces: one problem statement, three options with trade-offs, one
recommendation with definition of done and implementation plan.

Moved to optional-skills/ (niche communication framework, not broadly
needed by default). Improved description with clearer trigger conditions
and replaced implementation-specific example with a generic one.

Based on PR #1262 by Willardgmoore.

Co-authored-by: Willard Moore <willardgmoore@users.noreply.github.com>
@teknium1

Copy link
Copy Markdown
Contributor

Merged via PR #3797. Your skill was cherry-picked onto current main with authorship preserved — moved to optional-skills/communication/ with an improved description and a more generic example. Thanks for the contribution!

angelburgosrosado pushed a commit to angelburgosrosado/hermes-agent that referenced this pull request Apr 27, 2026
…h#3797)

Adds a structured 1-3-1 decision-making framework as an optional skill.
Produces: one problem statement, three options with trade-offs, one
recommendation with definition of done and implementation plan.

Moved to optional-skills/ (niche communication framework, not broadly
needed by default). Improved description with clearer trigger conditions
and replaced implementation-specific example with a generic one.

Based on PR NousResearch#1262 by Willardgmoore.

Co-authored-by: Willard Moore <willardgmoore@users.noreply.github.com>
angelburgosrosado pushed a commit to angelburgosrosado/hermes-agent that referenced this pull request Apr 28, 2026
Adds a structured 1-3-1 decision-making framework as an optional skill.
Produces: one problem statement, three options with trade-offs, one
recommendation with definition of done and implementation plan.

Moved to optional-skills/ (niche communication framework, not broadly
needed by default). Improved description with clearer trigger conditions
and replaced implementation-specific example with a generic one.

Based on PR NousResearch#1262 by Willardgmoore.
02356abc pushed a commit to 02356abc/hermes-agent that referenced this pull request May 14, 2026
…h#3797)

Adds a structured 1-3-1 decision-making framework as an optional skill.
Produces: one problem statement, three options with trade-offs, one
recommendation with definition of done and implementation plan.

Moved to optional-skills/ (niche communication framework, not broadly
needed by default). Improved description with clearer trigger conditions
and replaced implementation-specific example with a generic one.

Based on PR NousResearch#1262 by Willardgmoore.

Co-authored-by: Willard Moore <willardgmoore@users.noreply.github.com>
olympus-terminal pushed a commit to olympus-terminal/hermes-agent that referenced this pull request May 16, 2026
…h#3797)

Adds a structured 1-3-1 decision-making framework as an optional skill.
Produces: one problem statement, three options with trade-offs, one
recommendation with definition of done and implementation plan.

Moved to optional-skills/ (niche communication framework, not broadly
needed by default). Improved description with clearer trigger conditions
and replaced implementation-specific example with a generic one.

Based on PR NousResearch#1262 by Willardgmoore.

Co-authored-by: Willard Moore <willardgmoore@users.noreply.github.com>
CumulusService pushed a commit to Cumulus-Service-GmbH/hermes-agent that referenced this pull request May 30, 2026
Adds a structured 1-3-1 decision-making framework as an optional skill.
Produces: one problem statement, three options with trade-offs, one
recommendation with definition of done and implementation plan.

Moved to optional-skills/ (niche communication framework, not broadly
needed by default). Improved description with clearer trigger conditions
and replaced implementation-specific example with a generic one.

Based on PR NousResearch#1262 by Willardgmoore.
gweeteve pushed a commit to gweeteve/hermes-agent that referenced this pull request Jun 2, 2026
…h#3797)

Adds a structured 1-3-1 decision-making framework as an optional skill.
Produces: one problem statement, three options with trade-offs, one
recommendation with definition of done and implementation plan.

Moved to optional-skills/ (niche communication framework, not broadly
needed by default). Improved description with clearer trigger conditions
and replaced implementation-specific example with a generic one.

Based on PR NousResearch#1262 by Willardgmoore.

Co-authored-by: Willard Moore <willardgmoore@users.noreply.github.com>
Egavasyug pushed a commit to Egavasyug/hermes-agent that referenced this pull request Jun 10, 2026
…h#3797)

Adds a structured 1-3-1 decision-making framework as an optional skill.
Produces: one problem statement, three options with trade-offs, one
recommendation with definition of done and implementation plan.

Moved to optional-skills/ (niche communication framework, not broadly
needed by default). Improved description with clearer trigger conditions
and replaced implementation-specific example with a generic one.

Based on PR NousResearch#1262 by Willardgmoore.

Co-authored-by: Willard Moore <willardgmoore@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants