define-acceptance SKILL.md skillA
define-acceptance from tomzx/agents is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tomzx/agents/define-acceptance@git:20261007.b35fc4bPins git:20261007.b35fc4b in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tomzx/agents
- Path
skills/pdlc/skills/define-acceptance/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261007.b35fc4b, committed Oct 7, 2026
- First version recorded
- Aug 5, 2026
- Size
- 2,917 bytes
- Repository stars
- 12
- License
- MIT
Produce the acceptance contract — testable criteria that are the seam between PDLC and SDLC. PDLC owns what/why; SDLC owns how.
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
# Define Acceptance
This skill produces the **acceptance contract**: the testable, outcome-linked criteria that form the handoff from PDLC to SDLC.
It is the handoff.
SDLC's `create-requirements` consumes this contract directly.
The contract captures *what must be true* for the initiative to be accepted (linked to `SM-N` success metrics and `FR-N` requirements), expressed so an engineer and a PM can both verify it.
It deliberately excludes implementation.
## Prerequisites
- Apply the shared PDLC conventions in `skills/pdlc/references/shared.md`.
- `prd.md` with functional requirements and success criteria.
## Steps
1. Translate each functional requirement (`FR-N`) into one or more acceptance criteria in Given/When/Then or measurable form.
Each criterion must be verifiable by behavior or measurement, not by code inspection alone.
2. Bind each success metric (`SM-N`) to an acceptance criterion: "accepted only if `SM-N` reaches target within the window."
3. Bind guardrails: list every `GM-N` that must hold post-launch as a hard acceptance line ("must not regress below floor").
…Read the whole file at its exact version.
How to install
mdr add tomzx/agents/define-acceptance@sha256:528be4ac831f2afeThe line at the top of this page pins the label git:20261007.b35fc4b, 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_j6ujiexei54asxld)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between Aug 5, 2026 and Oct 7, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261007.b35fc4b latest | 2026-10-07 | b35fc4b | 2,917 B | A | view · diff |
| git:20261004.00bb0c5 | 2026-10-04 | 00bb0c5 | 2,909 B | A | view · diff |
| git:20260805.6b62307 | 2026-08-05 | 6b62307 | 2,904 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 (2917 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
tomzx/agents · 12 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_j6ujiexei54asxld GET https://markdownregistry.com/api/v1/resolve?ref=tomzx/agents/define-acceptance GET https://markdownregistry.com/api/v1/blob/528be4ac831f2afe6d3e34468a714a2cf4364819ed43ff118e0ce323e69b2fe8
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.