discover-acs skillA
discover-acs is agent-read markdown (skill) from swingerman/engineer: Use when a Ready feature needs its acceptance criteria discovered before specs are written. Triggers — "/engineer.discover-acs", "/engineer.acceptance-criteria", "discover ACs", "what must this feature do", "figure out acceptance criteria"..
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
# discover-acs Discover a feature's acceptance criteria — Checkpoint 2. ACs are **decisions about what behaviors must work**, in **domain language**. They precede the Given/When/Then formalization that `atdd:atdd` produces. Separating AC discovery (divergent decisions) from spec formalization (convergent encoding) is what protects domain language from leaking into implementation language. ## When to use On a feature with `autonomy_level` set and `status` of `ready` (greenfield) or `in-progress`/`done` (onboarded existing work). Produces `acs.md`. **Two modes:** - **Greenfield** — `status: ready`, no existing spec. Discover ACs from scratch via the four-pass interview. - **Reverse-engineer** — onboarded feature (`in-progress`/`done`) that already has a spec (a Speckit `spec.md`, a design doc, shipped code). Extract candidate ACs from the existing material, then interview only for the gaps it leaves. **Not for:** a parked feature (`discuss` to promote first); a feature that already has a complete `acs.md` (`feature-edit`); producing Given/When/Then specs (`atdd:atdd`); deciding whether to build the feature (`discuss`). ## Workflow …
Read the whole file at its exact version.
How to install
mdr add swingerman/engineer/discover-acs@git:20260823.7f6ca14mdr add swingerman/engineer/discover-acs@sha256:89b4fc37518c0626Pin 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_d55rliuhy6x6w7zb)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260823.7f6ca14 latest | 2026-08-23 | 7f6ca14 | 9,011 B | A | view · diff |
| git:20260729.715119e | 2026-07-29 | 715119e | 8,295 B | A | view · diff |
| git:20260604.4191d6a | 2026-06-04 | 4191d6a | 7,482 B | A | view · diff |
| git:20260528.0c6f513 | 2026-05-28 | 0c6f513 | 6,222 B | A | view · diff |
| git:20260520.cd41431 | 2026-05-20 | cd41431 | 5,846 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 (9011 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
swingerman/engineer · 150 stars · license MIT · pushed 2026-09-22 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_d55rliuhy6x6w7zb GET https://markdownregistry.com/api/v1/resolve?ref=swingerman/engineer/discover-acs GET https://markdownregistry.com/api/v1/blob/89b4fc37518c0626747ae6f50b9730dd062f403e0aa35adeef831cf459350dd9
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.