sop-rfc2119
RFC 2119 Keywords for SOPs
RFC 2119 defines keywords for indicating requirement levels in specifications. Using these keywords in SOPs creates precise, unambiguous instructions that AI agents can execute deterministically.
Key Concepts
The RFC 2119 Keywords
RFC 2119 defines these keywords for requirement levels:
| Keyword | Meaning | Usage |
|---|---|---|
| MUST | Absolute requirement | Non-negotiable steps that must be performed |
| MUST NOT | Absolute prohibition | Actions that are forbidden |
| SHOULD | Strong recommendation | Preferred approach, but alternatives may exist |
| SHOULD NOT | Strong discouragement | Discouraged, but may be acceptable in specific cases |
| MAY | Optional | Truly optional actions at agent's discretion |
Why Use RFC 2119 in SOPs
More from thebushidocollective/han
android-jetpack-compose
Use when building Android UIs with Jetpack Compose, managing state with remember/mutableStateOf, or implementing declarative UI patterns.
1.1Kfastapi-async-patterns
Use when FastAPI async patterns for building high-performance APIs. Use when handling concurrent requests and async operations.
786storybook-story-writing
Use when creating or modifying Storybook stories for components. Ensures stories follow CSF3 format, properly showcase component variations, and build successfully.
487atomic-design-fundamentals
Use when applying Atomic Design methodology to organize UI components into quarks, atoms, molecules, organisms, templates, and pages. Core principles and hierarchy.
367solid-principles
Use during implementation when designing modules, functions, and components requiring SOLID principles for maintainable, flexible architecture.
252angular-rxjs-patterns
Use when handling async operations in Angular applications with observables, operators, and subjects.
216