spec-loop SKILL.md skillA

spec-loop from kamioj/spec-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add kamioj/spec-workflow/spec-loop@git:20260910.a57f970

Pins git:20260910.a57f970 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: kamioj/spec-workflow
Path: codex/skills/spec-loop/SKILL.md
Versions recorded: 5
Latest version: git:20260910.a57f970, committed Sep 10, 2026
First version recorded: Jul 17, 2026
Size: 9,434 bytes
Repository stars: 20
License: a license file GitHub does not identify

Goal-driven autonomous round loop. Give it a goal + acceptance checklist + round budget (touchpoint 1), then it researches, implements, self-checks, and retrospects round after round — driven by a Stop-event hook, not by prompt discipline — until the final acceptance audit (touchpoint 2, the loop's ONLY independent verification) passes every item, or a fuse blows (round cap / no-progress / refusal-to-retrospect). Use when the goal is known but the path is not; a known plan one-pass change…

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

<!-- GENERATED from core/commands/loop.md — edit the core file and run node tools/generate.mjs; hand edits will be overwritten -->

# $spec-loop

Goal-driven autonomous iteration: `research → implement → verify → retrospect` per round, with a **file ledger as cross-round memory** and a **Stop-event hook as the round driver**. The HARD GATE moves up to the goal level — the user approves the goal/acceptance/budget once, then the loop runs unattended until final acceptance or a fuse.

**Positioning**: `$spec-workflow` = plan known, one pass, two touchpoints. `$spec-loop` = goal known, path unknown, N rounds, same two touchpoints. A bare self-feeding loop (ralph-style) = no acceptance checklist, no independent verification, no ledger — this command exists precisely to add those. **Never run two loops at once** (nor alongside another Stop-driven looper such as ralph-loop).

**Ledger format authority**: [`../spec-core/references/loop-spec.md`](../spec-core/references/loop-spec.md) — loop.md structure, write ownership (loop.md model-only / .loop-state driver-only), field rules.

## Invocation forms

| Form | Behavior |
|---|---|
| `$spec-loop <goal>` | cold start (below) |
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kamioj/spec-workflow/spec-loop@sha256:02153f19fc7e7d16

The line at the top of this page pins the label git:20260910.a57f970, 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.

Badge

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

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

Versions

The registry has recorded 5 versions of this file, between Jul 17, 2026 and Sep 10, 2026, about one every 14 days.

version	committed	commit	size	audit
git:20260910.a57f970 latest	2026-09-10	a57f970	9,434 B	A	view · diff
git:20260904.7dbcf3a	2026-09-04	7dbcf3a	9,389 B	A	view · diff
git:20260725.8c53a0d	2026-07-25	8c53a0d	9,399 B	A	view · diff
git:20260717.6ee7a9c	2026-07-17	6ee7a9c	8,660 B	A	view · diff
git:20260717.4ff32bc	2026-07-17	4ff32bc	7,663 B	A	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 (9434 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

kamioj/spec-workflow · 20 stars · license a license file GitHub does not identify · pushed 2026-09-21 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_p6uembdxzyk2wmqc
GET https://markdownregistry.com/api/v1/resolve?ref=kamioj/spec-workflow/spec-loop
GET https://markdownregistry.com/api/v1/blob/02153f19fc7e7d1667a58305307324a0b57aade72802126bbff6f8790f21f28f

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.