spec-workflow is agent-read markdown (skill) from komluk/scaffolding: OpenSpec lifecycle orchestration for /workflow chains. TRIGGER when: coordinating the analyst-architect-developer-reviewer chain or managing spec status transitions. SKIP: writing an individual spec artifact (use spec-research, spec-design, or spec-review)..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# OpenSpec Workflow Orchestration
Spec-driven development protocol for coordinating multi-agent workflows.
## UUID Enforcement
**CRITICAL**: The `conversation_id` MUST always be a UUID (format: `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`). NEVER use descriptive names, slugs, or human-readable strings. If no UUID is available, generate one with `uuidgen` or `python3 -c "import uuid; print(uuid.uuid4())"`. Self-check: does the conversation_id match the pattern `[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}`? If not, STOP and use a real UUID.
## Directory Structure
```
.scaffolding/conversations/{conversation_id}/specs/
proposal.md -- WHY + WHAT (analyst)
design.md -- WHAT + HOW (architect)
tasks.md -- checklist (architect)
```
## Status Lifecycle
Tracked in `.scaffolding/conversations/{conversation_id}/context.json`:
| Status | Meaning | Transition |
|--------|---------|------------|
| `exploring` | Research phase | -> `drafting` when proposal done |
| `drafting` | Design + tasks | -> `implementing` when tasks done |
| `implementing` | Code changes | -> `reviewing` when tasks complete |
| `reviewing` | Verification | -> `complete` when verified |
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
A 17 of 17 checks passed. Deterministic, no model, 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 (4323 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
komluk/scaffolding · 15 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_g4il7iibjfxwb2ay
GET https://markdownregistry.com/api/v1/resolve?ref=komluk/scaffolding/spec-workflow
GET https://markdownregistry.com/api/v1/blob/071406e5aa641fb188d2d841daa7753b11c5cca835d22ce380b8d44613bff9d2
Your agent 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.
komluk/scaffolding · skills/github-actions-template/SKILL.md · GitHub Actions CI pipeline templates and workflow YAML patterns. TRIGGER when: creating or editing a CI workflow…
tencentcloudbase/cloudbase-ai-toolkit · plugin/cloudbase/skills/spec-workflow/SKILL.md · Use when medium-to-large changes need explicit requirements, technical design, and task planning before implementation…
tencentcloudbase/cloudbase-ai-toolkit · connectors/cloudbase-intl/skills/references/spec-workflow/SKILL.md · Use when medium-to-large changes need explicit requirements, technical design, and task planning before implementation…
tencentcloudbase/cloudbase-ai-toolkit · config/source/skills/spec-workflow/SKILL.md · Use when medium-to-large changes need explicit requirements, technical design, and task planning before implementation…
tencentcloudbase/cloudbase-ai-toolkit · config/.claude/skills/spec-workflow/SKILL.md · Use when medium-to-large changes need explicit requirements, technical design, and task planning before implementation…
tzachbon/smart-ralph · plugins/ralph-specum/skills/spec-workflow/SKILL.md · This skill should be used when the user asks to "build a feature", "create a spec", "start spec-driven development"…
kamioj/spec-workflow · codex/skills/spec-workflow/SKILL.md · Full SDD workflow, end to end, requirement fully delegated. Open decisions are digested internally (auto triage — no…
ramboz/jig · skills/spec-workflow/SKILL.md · Drive the spec-driven lifecycle for any non-trivial work item: SPIDR-split a new spec into vertical slices, transition…
ramboz/jig · hosts/codex/plugins/jig/skills/spec-workflow/SKILL.md · Drive the spec-driven lifecycle for any non-trivial work item: SPIDR-split a new spec into vertical slices, transition…
