Requirements Writing Guidance — EARS & Requirement Quality

Source: Original guidance by JG Systems Consulting Ltd. (methods cited: EARS / Mavin et al. 2009; quality & verification guidance per NASA public-domain SE guidance) | Chapters: 6

When to use

Use this pack when you are writing or reviewing requirements and want them unambiguous, singular, and verifiable. It gives you the quality characteristics a requirement must pass, the EARS sentence patterns that remove most ambiguity, a defect catalogue for review, and how to make requirements verifiable and traceable. Best for behavioural/functional requirements; it points to the authoritative standards rather than reproducing them.

Prerequisites: none — this pack is plain Markdown; no MCP server, API key, or licence tier is needed at runtime.

How to Use This Skill

• Without arguments — load the EARS patterns and the quality checklist below.
• With a topic — ask about EARS event-driven, unambiguous, weak words, verifiability.
• With a chapter — ask for ch03 (the EARS patterns).

Supporting files: glossary.md, patterns.md, cheatsheet.md (the EARS pattern-picker + banned-words list).