requirements-writing SKILL.md skillA
requirements-writing from jgsystemsconsulting/jgs-se-knowledge-packs is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jgsystemsconsulting/jgs-se-knowledge-packs/requirements-writing@git:20261008.7fe1552Pins git:20261008.7fe1552 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jgsystemsconsulting/jgs-se-knowledge-packs
- Path
packs/requirements-writing/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261008.7fe1552, committed Oct 8, 2026
- First version recorded
- Jun 19, 2026
- Size
- 6,077 bytes
- Repository stars
- 71
- License
- a license file GitHub does not identify
Guidance on writing high-quality requirements: the requirement quality characteristics and the EARS (Easy Approach to Requirements Syntax) patterns — ubiquitous, event-driven, state-driven, optional-feature, unwanted-behaviour — for unambiguous, singular, verifiable requirements, plus defect/anti-pattern review and verification & traceability. Use when authoring or reviewing requirements. Original synthesis citing EARS (Mavin et al.) and NASA public-domain guidance; not a reproduction of…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
<!-- argument-hint: [topic, EARS pattern, or chapter number] --> # 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). …
Read the whole file at its exact version.
How to install
mdr add jgsystemsconsulting/jgs-se-knowledge-packs/requirements-writing@sha256:d5c9643fc59554a1The line at the top of this page pins the label git:20261008.7fe1552, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_q5pb7vit7trwnkip)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jun 19, 2026 and Oct 8, 2026, about one every 110 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261008.7fe1552 latest | 2026-10-08 | 7fe1552 | 6,077 B | A | view · diff |
| git:20260619.1f25514 | 2026-06-19 | 1f25514 | 6,030 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6077 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jgsystemsconsulting/jgs-se-knowledge-packs · 71 stars · license a license file GitHub does not identify · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_q5pb7vit7trwnkip GET https://markdownregistry.com/api/v1/resolve?ref=jgsystemsconsulting/jgs-se-knowledge-packs/requirements-writing GET https://markdownregistry.com/api/v1/blob/d5c9643fc59554a1b996c81c898c3de96196f5add5bc2537da137910504286f8
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.