writing-conformant-specs

RFC 2119-conformant specifications use standardized keywords (MUST, SHOULD, MAY, etc.) to express normative requirements with precision. Load the RFC 2119 guide, identify your requirements, and label each with the appropriate keyword to create verifiable, machine-checkable specs.

Normative content states binding requirements using RFC 2119 keywords; informative content provides guidance, examples, or rationale without mandatory force. Separating them clearly ensures readers distinguish what must be implemented from what's optional or explanatory.

MUST indicates mandatory requirements; SHOULD indicates strong recommendations that may be deviated from with justification; MAY indicates truly optional features. Use the decision-tree keyword guidance to map each requirement to the appropriate level of conformance.

Yes. Start with your plain-language requirements, identify the binding intent of each statement, and convert it to the corresponding RFC 2119 keyword with proper labeling. Iterative drafting lets you refine keywords and validate conformance as you work.

The skill provides templates and patterns for separating normative from informative sections, structuring requirements hierarchically, and labeling keywords consistently. These patterns guide layout and ensure your spec remains machine-checkable and auditable.

Use the validation checks included in the skill to verify keyword usage, confirm separation of normative and informative content, and ensure all requirements are verifiable. These checks produce actionable feedback to refine your spec before publication.