spec-finish SKILL.md skillA
spec-finish from martinffx/atelier is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add martinffx/atelier/spec-finish@git:20261018.a370713Pins git:20261018.a370713 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- martinffx/atelier
- Path
skills/spec-finish/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261018.45ccfce, committed Oct 18, 2026
- First version recorded
- Jul 27, 2026
- Size
- 4,391 bytes
- Repository stars
- 48
- License
- MIT
Post-implementation completion workflow for Spec-backed Plans. Use after spec-implement completes to validate, review, create stacked commits, and open a PR via code-pull-request. Triggers only with an active Spec-backed Plan after spec-implement completes, including when the user says "finish", "done", or "complete" in that context.
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
# Spec Finish Post-implementation workflow: simplify → synchronize docs → validate → review → prepare PR. ## Prerequisites Before starting, verify: 1. All Spec-backed Plan tasks are complete 2. Working directory has no unresolved staged or unstaged changes 3. Tests pass If not complete, go back to `spec-implement`. --- ## Step 1: Compare Scope and Simplify Compare the implementation with the original behavior and user goal before documentation or validation. Remove unrequested scope, duplicate concepts, one-consumer abstractions, and custom machinery that replaces sufficient platform behavior. If the implementation faithfully follows an unnecessarily large design, stop and return to `spec-plan`. Get approval for the smaller plan before continuing. Update the finished SDD to describe the smaller result. Replace rejected architecture in the normative design and plan instead of preserving it as precedent; mention it only as a rejected alternative when that history remains useful. --- ## Step 2: Update Documentation Check whether README, API documentation, or changelog updates are needed. Make and commit any …
Read the whole file at its exact version.
How to install
mdr add martinffx/atelier/spec-finish@sha256:aaeae599b38baa8bThe line at the top of this page pins the label git:20261018.a370713, 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.
[](https://markdownregistry.com/a/art_hspmcu4jefuqsmex)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Jul 27, 2026 and Oct 18, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261018.45ccfce latest | 2026-10-18 | 45ccfce | 4,391 B | A | view · diff |
| git:20261018.a370713 | 2026-10-18 | a370713 | 4,423 B | A | view · diff |
| git:20260809.fcf852b | 2026-08-09 | fcf852b | 4,291 B | A | view · diff |
| git:20260801.96f6fe8 | 2026-08-01 | 96f6fe8 | 3,498 B | A | view · diff |
| git:20260727.3faefd4 | 2026-07-27 | 3faefd4 | 3,488 B | A | view · diff |
| git:20260727.694e846 | 2026-07-27 | 694e846 | 3,434 B | A | view · diff |
| git:20260727.c30bc12 | 2026-07-27 | c30bc12 | 3,380 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 (4391 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
martinffx/atelier · 48 stars · license MIT · pushed 2026-10-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_hspmcu4jefuqsmex GET https://markdownregistry.com/api/v1/resolve?ref=martinffx/atelier/spec-finish GET https://markdownregistry.com/api/v1/blob/aaeae599b38baa8b861425f93edf7ed4a0b51a263af77d3450308ed65b9e7ca0
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.