sop-rfc2119

Enforce RFC 2119 keyword usage in standard operating procedures.

187|20|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/TheBushidoCollective/han --skill sop-rfc2119
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sop-rfc2119
Source: https://github.com/TheBushidoCollective/han/tree/main/hashi/hashi-agent-sop/skills/sop-rfc2119
Command: npx skills add https://github.com/TheBushidoCollective/han --skill sop-rfc2119

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Introduces deterministic SOPs using RFC 2119 keywords to express MUST, SHOULD, MAY guidance for AI agents.

Core Features & Use Cases

  • RFC 2119 Keywords: MUST, SHOULD, MAY usage guidelines.
  • Good Practices: Clear decision points and non-ambiguous steps.
  • SOP Clarity: Improves reproducibility and safety.

Quick Start

Draft an SOP that uses MUST for critical steps and SHOULD for recommended actions.

Frequently Asked Questions about sop-rfc2119

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What are RFC 2119 keywords and why do they matter for SOPs?

RFC 2119 keywords—MUST, MUST NOT, SHOULD, SHOULD NOT, MAY—standardize requirement language in SOPs to eliminate ambiguity. They let teams and AI agents classify actions as mandatory, recommended, or optional, ensuring reproducible execution and audit-ready compliance.

How do I write an SOP using RFC 2119 keywords?

Use MUST for critical, non-negotiable steps; SHOULD for recommended actions; MAY for optional ones. Structure each step with a clear decision point and the appropriate keyword so anyone—human or agent—executes the SOP deterministically without interpretation.

Can I use RFC 2119 keywords across governance, security, and quality workflows?

Yes. RFC 2119 keywords work across SOP creation, revision, and automation in governance, security, and quality assurance contexts. They enforce consistent requirement classification wherever deterministic, audit-ready SOPs are needed.

What's the difference between MUST, SHOULD, and MAY in SOP writing?

MUST marks mandatory actions with no deviation; SHOULD indicates best practices where exceptions are permissible; MAY denotes optional steps. This three-tier classification prevents vague language and enables agents to make deterministic decisions.

How do RFC 2119 keywords improve SOP clarity and safety?

RFC 2119 keywords eliminate subjective interpretation by codifying obligation levels. This improves reproducibility, reduces compliance gaps, supports deterministic agent behavior, and creates audit trails that satisfy governance and quality requirements.