spec-workflow-harness
v5.9.0Autonomous SDD harness for Spec Workflow MCP: the 'continue the sdd process' supervisor, one orchestrator agent per phase, and pinned worker agents. Ships no MCP server; use it with a project that configures spec-workflow in its own .mcp.json.
By Matthew FieldLicense: GPL-3.02 GitHub starsUpdated 1 hour ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Sep 24, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install spec-workflow-harness for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install spec-workflow-harness@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/madmatt112/spec-workflow-mcpClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/spec-workflow-harness/.
Plugin files
├── .claude-plugin/plugin.json├── skills/sdd-continue/SKILL.md└── skills/sdd-document-phase/SKILL.md
Included Skills2
Continue the spec-driven development (SDD) process for the active spec. A thin supervisor that resolves the spec store and code roots, finds the active spec and its live phase, spawns one phase orchestrator at a time, and runs the retrospective conversation. Use when the user says "continue the sdd process", "continue sdd", "run the sdd loop", "next sdd step", or when this skill is invoked by name.
Runs one SDD document phase (requirements, design, or tasks) of one spec to agent-side approval. Drafts v1, runs adversarial review and revision rounds with pinned worker agents, rules on standoffs, adjudicates past the v4 cap, approves the final version, prunes superseded approval records, cleans the reviews directory, and reports in the orchestrator contract. Used by the sdd-document-orchestrator agent, not directly from a main session.
Plugin manifests1
{
"name": "spec-workflow-harness",
"version": "5.9.0",
"description": "Autonomous SDD harness for Spec Workflow MCP: the 'continue the sdd process' supervisor, one orchestrator agent per phase, and pinned worker agents. Ships no MCP server; use it with a project that configures spec-workflow in its own .mcp.json.",
"author": {
"name": "Matthew Field"
},
"homepage": "https://github.com/madmatt112/spec-workflow-mcp",
"license": "GPL-3.0"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[spec-workflow-harness on Agent Plugins Marketplace](https://pluginsmp.com/plugins/spec-workflow-harness)