Home / arcasilesgroup / ai-engineering · GitHub

spec-extract SKILL.md skillA

Removed from GitHub on 2026-11-09. The file no longer exists in its repository, and every version below is still saved here. mdr add no longer finds it by name, but a lockfile that pins one of these versions still installs it from its recorded commit, for as long as GitHub keeps that commit.

spec-extract from arcasilesgroup/ai-engineering is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install the version recorded here
mdr add arcasilesgroup/ai-engineering/spec-extract@sha256:fb2a8ef42e96f075

Pins the contents saved here, the only way to install this file now it is gone from GitHub. What a pinned install does.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
arcasilesgroup/ai-engineering
Path
skills/ai-verify/tiers/1-standalone/spec-extract/SKILL.md
Versions recorded
1
Latest version
git:20260901.dca22e5, committed Sep 1, 2026
Size
9,633 bytes
Repository stars
65
License
Apache-2.0

Turn an unwritten agreement into a checkable spec — pull the requirements out of this conversation, a ticket, a pasted thread, or a design discussion, and write them to the project's spec file as numbered, falsifiable claims. Use before starting a feature, when the user says "write this up", "turn this into a spec", "make a design doc", "what did we agree", "capture the requirements", or "create design.md"; when a review skill halts because no spec exists; and at the point a conversation has…

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

# Extract a spec from what was actually agreed

`design-check` halts without a spec. `verify-feature` falls back to reconstructing one
from conversation memory, which is the weakest contract it supports. Both problems are the
same problem: the agreement exists, but only in a chat log that nobody will re-read and
that the next session cannot see.

Your job is to move it out of the conversation and into a file, without inventing
anything. The single failure mode of this skill is a confident spec containing
requirements nobody ever asked for — that is worse than no spec, because every downstream
verification then measures against fiction and reports it as fact.

## 1. Do not read the implementation first

If code already exists for this work, **do not read it before you have drafted the
requirement list.** You will reconstruct requirements that the code happens to satisfy,
and produce a spec that is guaranteed to pass its own check. This is the same ordering
rule as `verify-feature` §1 and it matters more here, because the artifact persists.

There is one legitimate exception, and it must be labeled. When the goal is explicitly to
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

The line at the top of this page is already the fingerprint pin, because a file GitHub no longer serves cannot be found by its label. With it 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_lftl7jqqqglnn5hq.svg)](https://markdownregistry.com/a/art_lftl7jqqqglnn5hq)

6 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Sep 1, 2026.

versioncommittedcommitsizeaudit
git:20260901.dca22e5 latest2026-09-01 dca22e5 9,633 BA view

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (9633 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

GitHub

arcasilesgroup/ai-engineering · 65 stars · license Apache-2.0 · pushed 2026-11-09 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_lftl7jqqqglnn5hq
GET https://markdownregistry.com/api/v1/resolve?ref=arcasilesgroup/ai-engineering/spec-extract
GET https://markdownregistry.com/api/v1/blob/fb2a8ef42e96f07515aad45263c3f7dd7e809da8c008a7ae859ab439c4221b76

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.

Browse by kind, by grade A, or by owner.