claude

spec-flow

Spec-driven multi-agent pipeline for Node projects: a feature ships only when a test that actually ran proves every requirement in its spec.

2 on GitHubby Ignacio MarínMITupdated yesterdaydevelopment
/

Plugin spec-flow from marketplace spec-flow-marketplace in IgnacioMarin402/spec-flow-plugin. Commands read from the repo's manifest — today.

This plugin runs code on your machine — its hooks fire automatically on events like tool use. The exact commands are listed below; read them before installing.

What it installs

Skills (2)

  • engine-comments

    Decide where a piece of reasoning belongs when writing or editing this engine — an invariant beside the code, a transition in the commit message, or a decision in decisions/. Use when adding a comment or a file header to cmd/, internal/, hooks/, commands/ or agents/, when a header has grown past wha

  • spec-flow-setup

    Set up or repair this repo's spec-flow contract — run init, fill the fields it could not read, make the test command emit a report the engine can read, and prove the result with a green check. Use when a repo has no .spec-flow/config.json, when init left MISSING or REVIEW lines, when a run refuses t

Slash commands (4)

  • /spec-flow:models

    Show which model tier each spec-flow agent will run on in this repo, and which layer decided it. Optionally set or clear one agent's tier.

  • /spec-flow:resume

    Resume a /spec-flow or /spec-fix run that a previous session left unfinished, at the step the disk says it reached — without starting over.

  • /spec-flow:spec-fix

    Lightweight fix flow — triage a defect against specs/, then one implementer pass through the same external gate. No planner, no reviewer, no milestone map.

  • /spec-flow:spec-flow

    Spec-driven multi-agent flow — free-text requirement -> spec (HITL) -> plan -> review -> implement per milestone, gated by an external lint/test loop.

Subagents (5)

  • architect

    The architect advisor (Opus; a project can route it to another tier, such as Fable). Answers the implementer's technical and design doubts with decisive guidance. Read-only — does not write feature code and does not re-plan.

  • implementer

    Implements the current milestone (Sonnet) following plan.md and the repo's own conventions. Writes code and tests. Escalates hard/complex design decisions to the architect instead of guessing. Runs only each new test alone, to see it fail; lint and the suite are an external gate's.

  • planner

    Senior planner (Opus). Turns an approved spec into a milestone-by-milestone implementation plan (M1..Mn). Also acts as the escalation consultant for the reviewer and the re-planner when the lint/test gate fails.

  • reviewer

    Reviews the plan for soundness (Sonnet, read-only). Approves, or escalates hard doubts to the planner instead of guessing.

  • spec-writer

    Owns the spec artifacts (Sonnet). MODE=SPEC turns a free-text requirement into a spec with user stories and requirement deltas. MODE=TRIAGE classifies a defect by what it does to specs/. MODE=FOLD verifies a shipped change landed in the capability specs under specs/, stamps its status and archives i

Hooks (21)

  • UserPromptSubmit

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook human-turn

  • SessionStart

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook session-start

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook no-gate-cmds

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook phase-guard

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook orchestrator-scope

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook preflight

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook opus-budget

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook arm-gate

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook dispatch-guard

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook model-route

  • PreToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook stale-resume

  • PostToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook lint-on-write

  • PostToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook register-agent

  • PostToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook human-turn

  • PostToolUse

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook run-trace

  • PostToolUseFailure

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook run-trace

  • SubagentStop

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook run-trace

  • SubagentStop

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook agent-gate

  • Stop

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook token-trace

  • Stop

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook human-turn

  • Stop

    "${CLAUDE_PLUGIN_ROOT}/bin/spec-flow" hook gate

View source on GitHub

Similar plugins

superpowers

claudecodex

Core skills library for Claude Code: TDD, debugging, collaboration patterns, and proven techniques

15 skills · hooks

obra/superpowers 316,836

context7

claudecodex

Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.

1 MCP server

upstash/context7 64,709

Build powerful, stateful CLI interfaces for any GUI application using the cli-anything harness methodology.

5 commands

HKUDS/CLI-Anything 58,665

Automates browser interactions for web testing, form filling, screenshots, and data extraction

12 skills

vercel-labs/agent-browser 50,373

Use Alibaba Open Code Review from local Codex.

2 skills

alibaba/open-code-review 50,068

slidev

claude

Claude Code skill for creating and presenting Slidev slidedecks

1 skill

slidevjs/slidev 49,452

Maintain spec-flow?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex pluginslisted