requirement-consistency-analysis skillA
requirement-consistency-analysis is agent-read markdown (skill) from naodeng/awesome-qa-skills: Use this skill when multiple requirement artifacts may disagree on terminology, identifiers, formats, states, rules, or behavior; triggers include requirement consistency, cross-document consistency, and consistency analysis..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Requirement Consistency Analysis Compare supplied requirements, contracts, designs, or rule artifacts to determine whether terminology, identifiers, formats, states, rules, and behavior agree within the same applicability scope. Preserve source and version boundaries; never silently merge mutually exclusive constraints. ## When to Use - PRDs, stories, API contracts, prototypes, technical notes, or acceptance criteria use different names or states. - You need to check whether multiple materials describe the same actor, field, flow, and outcome consistently. - The same flow may differ by version, time, platform, or role and applicability must be established first. Do not use it with one source when only general requirements analysis is needed, or to make a business decision for an explicit conflict. ## Output Format Options - Use Markdown by default; when a table, CSV, or JSON is requested, preserve the same evidence, status, impact, owner, and validation fields. - Do not present a structured format or static inventory as execution, pass, approval, or release evidence. ## How to Use …
Read the whole file at its exact version.
How to install
mdr add naodeng/awesome-qa-skills/requirement-consistency-analysis@git:20260914.45aa88fmdr add naodeng/awesome-qa-skills/requirement-consistency-analysis@sha256:3ae20af8aaab28b1Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_is5adomeccgx7wv6)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260914.45aa88f latest | 2026-09-14 | 45aa88f | 5,565 B | A | view · diff |
| git:20260914.72ab38e | 2026-09-14 | 72ab38e | 4,662 B | A | view · diff |
| git:20260914.ba5cf40 | 2026-09-14 | ba5cf40 | 4,511 B | A | view · diff |
| git:20260914.2a838ba | 2026-09-14 | 2a838ba | 3,308 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 (5565 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
naodeng/awesome-qa-skills · 230 stars · license NOASSERTION · pushed 2026-09-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_is5adomeccgx7wv6 GET https://markdownregistry.com/api/v1/resolve?ref=naodeng/awesome-qa-skills/requirement-consistency-analysis GET https://markdownregistry.com/api/v1/blob/3ae20af8aaab28b1c260d054615640a0a96fec00b9fdf833e3ad28d7201a8cdb
Your agent 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.