spec-critic skillA
spec-critic is agent-read markdown (skill) from vmobifystudio/app-dev-team: Use after the impl specs and the board exist but before any developer is spawned, to find every question a developer would otherwise be forced to guess at — error types, empty/failure states, cancel paths, source of truth, units, offline, atomicity. Produces `question` rows in the team ledger for tech-lead to answer in one batch. Triggers from /app-plan and from tech-lead whenever a sprint is about to start..
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
# Spec critic `tech-lead` runs this. **Do not create an agent for it** — tech-lead wrote the impl specs and is the role that answers these questions anyway, so a new role costs a spawn and buys a relay. Run it **once per sprint**, after `docs/22-impl-spec-*.md` and `docs/31-board.md` exist and before `/app-build` spawns anyone. Not once per ticket. ## Why it exists Measured across three dry runs and ten agent-runs, the live team channel was used **zero times** — including a run where the agent hit a planted ambiguity, decided it should raise it, and then reported that it had, when it had not. An agent that can proceed will proceed. The full story is in `skills/team-protocol/SKILL.md` § "Why ICs mostly won't message" and `docs/research/2026-07-29-dry-run-3-full-sprint.md`. "Declare, don't dispatch" catches the guess *after* it was made. This catches it before, while an answer still costs one line instead of a review-and-rework cycle. ## What you hunt For each ticket on the board, read its acceptance criteria and the spec section it points at, then ask what a developer would have to invent. **Ground every question in an acceptance criterion — a …
Read the whole file at its exact version.
How to install
mdr add vmobifystudio/app-dev-team/spec-critic@git:20260729.32eb18amdr add vmobifystudio/app-dev-team/spec-critic@sha256:79815f0801e889d1Pin 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_fe7y6rw2izsszdby)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260729.32eb18a latest | 2026-07-29 | 32eb18a | 5,999 B | A | view · diff |
| git:20260729.dc21f65 | 2026-07-29 | dc21f65 | 5,012 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 (5999 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
vmobifystudio/app-dev-team · 4 stars · license MIT · pushed 2026-09-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_fe7y6rw2izsszdby GET https://markdownregistry.com/api/v1/resolve?ref=vmobifystudio/app-dev-team/spec-critic GET https://markdownregistry.com/api/v1/blob/79815f0801e889d1cdd794f2dd99a3f55b5c7850e4fa716b513713957d9ffeaa
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.