spec-workflow

spec-workflow is a skill for Claude Code, Codex from komluk/scaffolding. It costs 55 tokens per session (1,075 once invoked), scanned A, original, MIT.

A workflow manager for OpenSpec, a system for describing software changes before building them. It coordinates research, design, implementation, and review using tracked status stages.

In plain words
What is it for?
Use it to coordinate analyst, architect, developer, and reviewer work, manage specification files, and move a change from exploration to completion.
Why use it?
It keeps multi-step specification work organized and makes each stage and handoff explicit.

Skill for Claude CodeCodex

Part of the scaffolding plugin — 35 skills, 9 commands, 13 agents shipped together

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/komluk/scaffolding/spec-workflow
Any agent
npx skills add komluk/scaffolding --skill spec-workflow
Clone the repo
git clone --depth 1 https://github.com/komluk/scaffolding

Made for: Claude Code, Codex.

Or install scaffolding, the plugin that ships this one along with the rest of its 35 skills, 9 commands, 13 agents.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for spec-workflow

README.md
[![agentmods](https://agentmods.dev/badge/skills/komluk/scaffolding/spec-workflow.svg)](https://agentmods.dev/skills/komluk/scaffolding/spec-workflow)
Your own site
<a href="https://agentmods.dev/skills/komluk/scaffolding/spec-workflow"><img src="https://agentmods.dev/badge/skills/komluk/scaffolding/spec-workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,075 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00055 $0.01075
Opus 5 $0.00028 $0.00537
Sonnet 5 $0.00011 $0.00215
Haiku 4.5 $0.00006 $0.00108

Measured 4d ago against content hash 071406e5aa64, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

spec-workflow scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/spec-workflow/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

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
complete Done -> archived on request
archived Historical Terminal state

Agent Routing in /workflow

Phase Agent Reads Writes Gate
1. Analyze analyst requirements proposal.md proposal written
1b. Research (conditional) researcher requirements ResearchPack score >= 80
2. Design architect proposal.md design.md, tasks.md score >= 85
3. Apply developer tasks.md, design.md source code validation passes
4. Verify reviewer design.md, tasks.md review report no criticals

When Researcher Is Needed

Analyst flags need for research in proposal.md. Researcher is invoked ONLY when the task involves:

  • New external API integration (e.g., Stripe, Twilio)
  • Unfamiliar library not yet in the project
  • Best practices requiring current internet research
  • Version-specific documentation for upgrades/migrations

Read the full file on GitHub · 100 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 4d ago First seen · 100 lines · 55 tokens per session scan A 071406e5aa64

Subscribe to this mod's changes

spec-workflow is a skill published in the GitHub repository komluk/scaffolding (15 stars, last pushed 29d ago), licensed MIT. It adds 55 tokens to every session and 1,075 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

seo-strategy

Audits and improves organic search performance — technical health, site architecture, internal linking, structured data, and the content decisions that determine what can rank. Use this to run an SEO audit, diagnose why pages are not ranking or were deindexed, plan a site's URL and navigation structure, add structured…

cbrock84/headcount · 74 tokens

implement-factory

Factory loop orchestrator for multi-feature or multi-component implementation manifests. Use for high-complexity work with parallel-eligible workstreams and holdout-scenario evaluation.

rsmdt/the-startup · 37 tokens

scenario-planning

Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold…

cbrock84/headcount · 78 tokens

ai-ml-governance

Governs models and AI systems in production — intended use, evaluation, monitoring, human oversight, documentation, and the decision to deploy or retire. Use this before deploying a model or AI feature, when defining evaluation criteria, when a model's behavior has drifted, when assessing AI risk or regulatory…

cbrock84/headcount · 83 tokens

ai-research-analyst

Produces executive-level research — market sizing, competitor mapping, trend analysis, and strategic intelligence — grounded in cited sources with the confidence in each claim made explicit. Use this to analyze a market or industry, map competitors, evaluate a market-entry or build-versus-buy decision, produce a…

cbrock84/headcount · 91 tokens

support-operations

Designs and runs the support function — channels, queues, routing, staffing, service levels, quality, and the metrics that show whether it is working. Use this to set up or fix support operations, choose channels, size a team, set or renegotiate service levels, reduce cost per contact, diagnose long queues or poor…

cbrock84/headcount · 77 tokens