spec-superflow

A specification-first coding workflow that connects planning with implementation, testing, debugging, review, and keeping specifications in sync. TDD means writing tests before the code they check; SDD means using a written specification to guide development.

In plain words
What is it for?
It helps validate schemas, plan changes, implement with TDD and SDD, debug systematically, review code, and synchronize updated specifications.
Why use it?
It provides a defined sequence for turning a plan into tested and reviewed code, reducing gaps between intended behavior and implementation.

Plugin for Claude Code

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 plugins/magebyte-zero/spec-superflow/marketplace
Claude Code
/plugin marketplace add MageByte-Zero/spec-superflow
Clone the repo
git clone --depth 1 https://github.com/MageByte-Zero/spec-superflow

Made for: Claude Code.

Per session not measured What this adds to a session before it is invoked.
When invoked not measured Not applicable: nothing here is loaded into a session.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Security

Grade A, and why

spec-superflow 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 yesterday.

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.

.claude-plugin/marketplace.json · 21 lines

What it actually says

{
  "name": "spec-superflow",
  "description": "Spec-first workflow: integrates OpenSpec planning engine + Superpowers execution discipline. 9 collaborative skills with embedded TDD, SDD, code review, debugging, and delta spec sync.",
  "owner": {
    "name": "MageByte",
    "url": "https://github.com/MageByte-Zero"
  },
  "plugins": [
    {
      "name": "spec-superflow",
      "description": "8-state workflow engine with 9 collaborative skills. Bridges planning and execution via execution-contract.md. Embedded schema validation, TDD, SDD, code review, systematic debugging, and delta spec sync.",
      "version": "1.0.1",
      "source": "./",
      "author": {
        "name": "MageByte",
        "url": "https://github.com/MageByte-Zero"
      }
    }
  ]
}
Files

What ships with it

1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. yesterday First seen · 21 lines scan A 0f1aec290aa2

Subscribe to this mod's changes

spec-superflow is a plugin published in the GitHub repository MageByte-Zero/spec-superflow (776 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.