requirement-summarizer
Installation
SKILL.md
Requirement Summarizer
A spec is hundreds of pages. The engineering-relevant content is the normative statements — the MUSTs, SHOULDs, and MUST NOTs. Everything else is context. Summarizing means extracting and organizing the normative core.
Normative vs informative
| Text type | Normative? | Include in summary? |
|---|---|---|
| "The server MUST ..." | Yes | Yes — this is a requirement |
| "The server SHOULD ..." | Yes | Yes — recommended, note as SHOULD |
| "The server MAY ..." | Yes | Brief mention — optional feature |
| "For example, ..." | No | Skip (unless the spec says examples are normative) |
| "Historically, ..." | No | Skip — background |
| "Implementations typically ..." | No | Skip — observation, not obligation |
| Definitions | Semi | Include the ones referenced by MUSTs |
Signal words: RFC 2119 keywords (MUST, SHALL, REQUIRED, SHOULD, MAY, OPTIONAL) are the gold standard. Specs that don't use them — look for imperative mood ("do X"), "is required", "is mandatory".