rfc2119

Audit technical documents for correct RFC 2119 keyword usage.

3|1|Updated Apr 12, 2026

Search Tags:#specification #requirements #technical writing #documentation quality #standards enforcement #rfc2119

Ready to run

npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill rfc2119-cogni-ai-ou

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: rfc2119
Source: https://github.com/Cogni-AI-OU/cogni-ai-agent-skills/tree/main/rfc2119
Command: npx skills add https://github.com/Cogni-AI-OU/cogni-ai-agent-skills --skill rfc2119-cogni-ai-ou

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents ambiguity and inconsistent enforcement of requirement-level terms by ensuring RFC 2119 keywords are used with their precise intended meanings in documentation and specifications.

Core Features & Use Cases

Keyword enforcement: Applies the standardized meaning of RFC 2119 requirement level keywords such as MUST, SHOULD, and MAY to technical writing.
Correct usage rules: Ensures absolute requirements, absolute prohibitions, strong/weak recommendations, and optionality are expressed with the right keywords and capitalization.
Safety-aware guidance: Promotes clear security implications when requirement directives are ignored, especially for MUST/MUST NOT/SHOULD/SHOULD NOT statements.
Use Case: While reviewing a new engineering spec or standards document, use this Skill to detect incorrect or weakened requirement language that could cause interoperability issues.

Quick Start

Use the rfc2119 skill to audit a standards document for incorrect RFC 2119 requirement keyword usage and recommend precise replacements.

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 keyword usage in technical specifications?▼

To enforce RFC 2119 keyword usage in technical specifications, audit your documents to ensure absolute requirements, prohibitions, and recommendations use the correct MUST, SHOULD, or MAY keywords with proper capitalization to remove ambiguity.

What is the correct way to use MUST and SHOULD in standards documentation?▼

In standards documentation, MUST denotes an absolute requirement while SHOULD signifies a strong recommendation. Correct usage requires precise keyword mapping and capitalization to accurately express requirement levels and prevent interoperability issues.

How do I check my engineering spec for incorrect requirement language?▼

Check your engineering spec for incorrect requirement language by auditing the document for weakened or misapplied RFC 2119 keywords, verifying necessity for inclusion, and recommending precise replacements to enforce documentation quality.

Why do requirement directives need security-context elaboration in technical writing?▼

Requirement directives need security-context elaboration in technical writing to clearly promote safety implications when MUST or SHOULD NOT directives are ignored, ensuring security and interoperability risks are explicitly documented for implementers.

Can I use this RFC 2119 standardization process for policy documents?▼

Yes, you can use this RFC 2119 standardization process for policy documents. It applies to reviewing and authoring any standards or policy documents where requirement-level intent affects interoperability, safety, or compliance.