rfc2119

Enforce RFC 2119 keyword capitalization and usage in technical documents.

1|Updated Mar 7, 2026

Search Tags:#documentation #standards #technical-writing #rfc2119 #uppercase #normative-language #rfc8174

Ready to run

npx skills add https://github.com/kayaman/skills --skill rfc2119

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rfc2119
Source: https://github.com/kayaman/skills/tree/main/skills/rfc2119
Command: npx skills add https://github.com/kayaman/skills --skill rfc2119

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill ensures correct and unambiguous use of RFC 2119 keywords (MUST, SHOULD, MAY, etc.) in technical documentation and standards.

Core Features & Use Cases

Standardization: Enforces consistent capitalization and usage of normative terms across docs, ADRs, API contracts, and design specifications.
Quality Assurance: Helps reviewers identify ambiguous language and ensures explicit, testable requirements.
Use Case: When drafting a specification, apply this skill to verify that all requirement levels are clearly defined and compliant with RFC 2119 and RFC 8174.

Quick Start

Enforce RFC 2119 terminology and capitalization in your documents.

Frequently Asked Questions about rfc2119

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

FAQPage Schema

How do I enforce RFC 2119 keywords in technical documentation?▼

RFC 2119 keywords are standardized terms (MUST, SHOULD, MAY) used in technical specifications to define normative requirements. They ensure unambiguous communication of requirement levels, making standards and API contracts explicitly clear and testable for reviewers.

What is the difference between RFC 2119 and RFC 8174 for normative language?▼

RFC 8174 clarifies RFC 2119 by requiring keywords to be uppercase only when normative. This skill applies both standards to your documentation, ensuring proper boilerplate references and avoiding ambiguous lowercase forms in technical standards and design documents.

When do I need to use RFC 2119 capitalization in API contracts?▼

You need RFC 2119 capitalization in API contracts and ADRs whenever you define normative requirements. This skill ensures terms like MUST and SHOULD are consistently capitalized, verifying that all requirement levels are clearly defined and compliant with standards.

Does this skill work for reviewing existing design specifications?▼

Yes, this skill works for quality assurance during reviews of existing design specifications. It helps reviewers identify ambiguous language, enforce consistent capitalization of normative terms, and ensure all requirement levels are clearly defined per RFC 2119 and RFC 8174.

How do I avoid lowercase forms of RFC 2119 terms in technical writing?▼

To avoid lowercase forms of RFC 2119 terms in technical writing, use this skill to scan documents and enforce uppercase usage. It provides guidance on proper boilerplate references and ensures explicit, testable requirements across all your technical standards and API contracts.