requirement-forge-refiner 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-forge-refiner 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-forge-refiner@git:20260903.83fa756Pins git:20260903.83fa756 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- techygarg/lattice
- Path
source/refiners/requirement-forge-refiner/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260903.83fa756, committed Sep 3, 2026
- Size
- 11,860 bytes
- Repository stars
- 206
- License
- MIT
Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution, customising its embedded defaults for the team's product process. Use when setting up a new project, defining product standards, or when the user says 'set up requirement standards'…
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 Forge Refiner ## What This Produces - **Output**: `.lattice/standards/requirement-standards.md` (or custom path from `.lattice/config.yaml` → `paths.requirement_standards`) - **Two modes**: - **Overlay** (`mode: overlay`): A slim document containing only sections that differ from the built-in defaults. The `requirement-quality` atom reads its embedded `defaults.md` first, then applies this document's sections on top. This is the expected common case. - **Override** (`mode: override`): A comprehensive standalone document that fully replaces the atom's embedded defaults. For teams whose product process differs fundamentally from the defaults. - **Default mode**: Overlay — produces only what the team wants to change - **Config key**: `paths.requirement_standards` in `.lattice/config.yaml` - **Consumed by**: `requirement-quality` atom (via config resolution) → `requirement-forge` molecule (composes the atom) - **Template**: Read `./assets/template.md` for the full document structure, default content, and interview guidance comments ## Scope Clarification This refiner defines how requirements are *structured and expressed* for this project. It does not define: …
Read the whole file at its exact version.
How to install
mdr add techygarg/lattice/requirement-forge-refiner@sha256:75302dbf154b6a7bThe line at the top of this page pins the label git:20260903.83fa756, 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_qksjfq6antbryd7u)
1 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 (11860 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_qksjfq6antbryd7u GET https://markdownregistry.com/api/v1/resolve?ref=techygarg/lattice/requirement-forge-refiner GET https://markdownregistry.com/api/v1/blob/75302dbf154b6a7b500ec74cae777f3b3c47d7896e0b2a6ec2a15aab7f7f5852
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