requirement-quality SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
requirement-quality from techygarg/lattice is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add techygarg/lattice/requirement-quality@git:20260903.6d09876Pins git:20260903.6d09876 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- techygarg/lattice
- Path
skills/requirement-quality/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260903.6d09876, committed Sep 3, 2026
- Size
- 8,918 bytes
- Repository stars
- 206
- License
- MIT
Apply requirement quality principles when generating or validating feature specifications. Enforces feature completeness, scenario structure, AC verifiability, feature independence, and implementation slice quality. Use when writing feature specs, validating existing requirements, or when the user mentions 'validate this spec', 'check this feature', 'requirement quality', 'is this spec complete', or 'requirement-quality'. This skill governs the craft of writing individual feature…
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
# Requirement Quality ## Config Resolution Skill supports project-specific standards. Order: 1. Look for `.lattice/config.yaml` in the repo root 2. If found, check `paths.requirement_standards` for a custom document path 3. If a custom document exists at that path, read it and check its YAML frontmatter for `mode`: - **`mode: override`**: the custom document has full precedence. Use it instead of the embedded defaults. It must be comprehensive — treat it as the sole reference. - **`mode: overlay`** (or no mode field): read the embedded `./references/defaults.md` first, then apply the custom document's sections on top. A custom section replaces the matching default section (matched by exact heading); new sections append after the defaults. 4. If a custom path is configured but no document exists at it → tell the user which configured path is missing, then fall back to `./references/defaults.md` 5. If there is no config file or no `paths.requirement_standards` key → read `./references/defaults.md` Custom standards produced by `requirement-forge-refiner` → consumed by this atom → composed by `requirement-forge` molecule. ## Self-Validation Checklist …
Read the whole file at its exact version.
How to install
mdr add techygarg/lattice/requirement-quality@sha256:ed07e16d0bb17691The line at the top of this page pins the label git:20260903.6d09876, 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_hb5p666alg75k25b)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 3, 2026.
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 (8918 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
techygarg/lattice · 206 stars · license MIT · pushed 2026-10-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hb5p666alg75k25b GET https://markdownregistry.com/api/v1/resolve?ref=techygarg/lattice/requirement-quality GET https://markdownregistry.com/api/v1/blob/ed07e16d0bb17691580eb098e48d97e619f2440f0cc8f46fcbaec11a284064a4
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.
More from techygarg/lattice
Every file in techygarg/lattice