spec-workflow SKILL.md skillA
spec-workflow from kamioj/spec-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kamioj/spec-workflow/spec-workflow@git:20260921.886d28dPins git:20260921.886d28d 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-workflow/SKILL.md- Versions recorded
- 6
- Latest version
- git:20260921.886d28d, committed Sep 21, 2026
- First version recorded
- Jul 14, 2026
- Size
- 6,298 bytes
- Repository stars
- 20
- License
- a license file GitHub does not identify
Full SDD workflow, end to end, requirement fully delegated. Open decisions are digested internally (auto triage — no mid-flight questions); MUST stop at exactly two points — the HARD GATE and acceptance/archive. The user participates as an evaluator; evaluation rounds are unlimited. Also accepts the legacy $sdd entry point. Trigger words: spec first / proposal / design first / draft a plan.
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/workflow.md — edit the core file and run node tools/generate.mjs; hand edits will be overwritten --> # $spec-workflow Task: $ARGUMENTS ## When to use Large changes (>150 lines / touching 3+ files / introducing new dependencies / architectural decisions). Trivial / small / medium tasks should be handled directly — **NEVER activate this workflow for those**. ## Execution order Invoke each phase command in the order below. **If any phase encounters user rejection or a placeholder scan / HARD GATE failure → stop and report; do not push through**. 1. **`$spec-research <direction>`** — survey industry practices + key constraints + flag `[TBD]` pending decisions 2. **`$spec-ask` in auto-triage mode** — do NOT interrogate the user; triage every `[TBD]` into `## Decided` per ask.md § Auto triage: factual → evidence; reversible preference → decide + `auto` mark; irreversible / product-semantics → decide + `escalated` mark (surfaced at the gate, standing unless overturned). Every self-decision passes the four-question filter; "don't do it / minimal" is always a candidate …
Read the whole file at its exact version.
How to install
mdr add kamioj/spec-workflow/spec-workflow@sha256:3baa377d16da7c87The line at the top of this page pins the label git:20260921.886d28d, 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_zzpspvkfzmqnh2ui)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Jul 14, 2026 and Sep 21, 2026, about one every 14 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.886d28d latest | 2026-09-21 | 886d28d | 6,298 B | A | view · diff |
| git:20260910.a487b6b | 2026-09-10 | a487b6b | 6,129 B | A | view · diff |
| git:20260910.a57f970 | 2026-09-10 | a57f970 | 5,441 B | A | view · diff |
| git:20260904.f4c79c8 | 2026-09-04 | f4c79c8 | 5,399 B | A | view · diff |
| git:20260725.8c53a0d | 2026-07-25 | 8c53a0d | 5,405 B | A | view · diff |
| git:20260714.a0e0c5f | 2026-07-14 | a0e0c5f | 5,112 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 (6298 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
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_zzpspvkfzmqnh2ui GET https://markdownregistry.com/api/v1/resolve?ref=kamioj/spec-workflow/spec-workflow GET https://markdownregistry.com/api/v1/blob/3baa377d16da7c877f424f435f15c5ae0b55c5fa29e8dab7e9b4ad2c3e2dea7f
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.
More from kamioj/spec-workflow
Every file in kamioj/spec-workflow