spec-revise SKILL.md skillA

spec-revise 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-revise@git:20260714.a0e0c5f

Pins git:20260714.a0e0c5f 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-revise/SKILL.md
Versions recorded: 2
Latest version: git:20260714.a0e0c5f, committed Jul 14, 2026
First version recorded: Jul 9, 2026
Size: 2,925 bytes
Repository stars: 20
License: a license file GitHub does not identify

Edit a single proposal.md section (why / what / how / risk). A full rewrite goes through $spec-propose. After editing, the HARD GATE must run again.

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/revise.md — edit the core file and run node tools/generate.mjs; hand edits will be overwritten -->

# $spec-revise

Target section: $ARGUMENTS

## Flow

1. Parse the parameter:

| Parameter | Section edited |
|---|---|
| `why` | `## Why` |
| `what` | `## What` |
| `how` | `## How` |
| `risk` | `## Risk` |
| none | ask the user which section to edit by presenting numbered options: "Which section to edit? 1) why  2) what  3) how  4) risk" |

2. Read `spec/changes/<name>/proposal.md`, locate the target section
3. **Remove the old `<!-- APPROVED: ... -->` approval marker** (any revision invalidates the old approval)
4. Edit the target section, **leaving the other sections untouched**
5. **Re-emit the HARD GATE**

## HARD GATE re-emission

Any revision must pass through the HARD GATE again:

```
<HARD-GATE>
=== Proposal revised (<section>) ===
Path: spec/changes/<name>/proposal.md
Changes — same explanation layer as propose's gate, scoped to the edit:
  <the revised decision in one plain sentence>
  Problem: <when who does what, because of what, what goes wrong — ≤2 lines>
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add kamioj/spec-workflow/spec-revise@sha256:167123ed2d14513d

The line at the top of this page pins the label git:20260714.a0e0c5f, 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_ifqehcgsaf22golp.svg)](https://markdownregistry.com/a/art_ifqehcgsaf22golp)

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

Versions

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

version	committed	commit	size	audit
git:20260714.a0e0c5f latest	2026-07-14	a0e0c5f	2,925 B	A	view · diff
git:20260709.322dd02	2026-07-09	322dd02	2,832 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 (2925 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_ifqehcgsaf22golp
GET https://markdownregistry.com/api/v1/resolve?ref=kamioj/spec-workflow/spec-revise
GET https://markdownregistry.com/api/v1/blob/167123ed2d14513d223a5d0429f082b800a593e510ea5764fc7f4c798b147ad4

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.