spec-core SKILL.md skillA
spec-core 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-core@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-core/SKILL.md- Versions recorded
- 7
- Latest version
- git:20260921.886d28d, committed Sep 21, 2026
- First version recorded
- Sep 4, 2026
- Size
- 38,675 bytes
- Repository stars
- 20
- License
- a license file GitHub does not identify
Spec-driven development workflow overview. Load this skill ONLY when the user explicitly asks for the spec flow — says "spec this first / draft a proposal / design first / write a proposal", or invokes a $spec-x command. NEVER self-activate on task size or complexity: size is at most grounds for a one-line suggestion, and silence means proceed without spec. Teaches the sdd plugin's 16 commands, artifact map, and Shared Principles (HARD GATE / interrogation / Stuck Protection / Anti-Cheating).
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/skill.md — edit the core file and run node tools/generate.mjs; hand edits will be overwritten -->
# SDD Plugin Overview
Spec-driven development workflow: research → interrogate → propose → HARD GATE → implement → verify → archive. A multi-command plugin where every stage fires independently.
## When to use
**Activation is user-explicit ONLY** — the flow starts when the user invokes a `$spec-x` command or says "spec this first | proposal | design first | draft a solution". **The model NEVER self-activates this workflow**, no matter how large the task looks.
Size signals (>150 lines / 3+ files / new dependency / architecture choice) are grounds for **at most a one-line suggestion** ("this is large — want the spec flow?"). No answer = no spec: just do the work. Auto-drifting a task into spec ceremony uninvited is this plugin's single biggest failure mode — worse than skipping spec on a large change, because the user can always invoke spec later, but time burned on unwanted process is gone.
…Read the whole file at its exact version.
How to install
mdr add kamioj/spec-workflow/spec-core@sha256:a313114e1bafca49The 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_72ruszu6tklqsywd)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Sep 4, 2026 and Sep 21, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.886d28d latest | 2026-09-21 | 886d28d | 38,675 B | A | view · diff |
| git:20260921.0a26974 | 2026-09-21 | 0a26974 | 35,733 B | A | view · diff |
| git:20260910.0880988 | 2026-09-10 | 0880988 | 35,594 B | A | view · diff |
| git:20260910.a57f970 | 2026-09-10 | a57f970 | 34,574 B | A | view · diff |
| git:20260909.ad954af | 2026-09-09 | ad954af | 32,586 B | A | view · diff |
| git:20260909.4201437 | 2026-09-09 | 4201437 | 31,772 B | A | view · diff |
| git:20260904.f4c79c8 | 2026-09-04 | f4c79c8 | 31,400 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 (38675 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_72ruszu6tklqsywd GET https://markdownregistry.com/api/v1/resolve?ref=kamioj/spec-workflow/spec-core GET https://markdownregistry.com/api/v1/blob/a313114e1bafca4990a5c5e3973c11df9418a260e32ba7998eef6ab2cc255c70
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.