Springfield plugin for planning, starting, inspecting, and recovering project work.
Use Springfield plan-from-jira to compile one or more Jira tickets, or an epic and its children, into a runnable batch.
Use Springfield plan to compile a new work request into a runnable batch for the current project.
Use Springfield recover to diagnose a stuck batch or failed slice and restore a safe next step.
Use Springfield status to inspect the active batch and explain where it stands.
Use Springfield plan-from-jira to compile one or more Jira tickets, or an epic and its children, into a runnable batch.
Use Springfield plan to compile a new work request into a runnable batch for the current project.
Use Springfield recover to diagnose a stuck batch or failed slice and restore a safe next step.
Use Springfield status to inspect the active batch and explain where it stands.
Executes bash commands
Hook triggers when Bash tool is used
Modifies files
Hook triggers on file write and edit operations
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.

Local-state conductor for multi-agent code work, distributed as a Claude Code (and Codex) marketplace plugin.
Springfield turns a plan (file or prompt) into a sequential batch of agent runs, executes each slice in an isolated git worktree, captures per-slice evidence, and falls through agent_priority (default: Claude → opt-in Codex → opt-in Gemini) when a run is retryable. State lives under .springfield/ in the repo; install ships through Claude Code and Codex marketplace plugins.
Vendor economics:
claude -pheadless invocations count against the Claude Max/Pro subscription, so Springfield defaults to Claude (Codex and Gemini are opt-in). Anthropic briefly meteredclaude -pseparately (2026-05-14) before reverting; Springfield keeps that response — a Codex-led default plus aspringfield startbilling warning — one flag flip away (ClaudeHeadlessMeteredininternal/core/agents) for if it returns.--cost-cap $Xaborts the batch when spend hits the threshold regardless.
"Plugin-distributed" here means Springfield is installed via the marketplace plugin flow. Springfield does not currently expose a plugin or extension API of its own.
When you run springfield start, the conductor will:
springfield/<plan-id> so the host clone stays untouched.agent_priority (default: Claude; Codex/Gemini opt-in) against the plan envelope..springfield/execution/plans/<plan-id>/evidence/iter-<N>/ and watch for the runner-sole-writer markers that signal pass/fail.Pre-1.0. Config and state layout may change without migration shims.
npm install -g @anthropic-ai/claude-code)GEMINI_API_KEY or sign in headless)brew install path. Linux/Windows install the CLI via Alternate Install Paths.go install .); not needed for the brew install path.springfield # Show help and next-step guidance
springfield init # Scaffold springfield.toml and .springfield/
springfield install # Sync local Claude Code/Codex host artifacts
springfield doctor # Check local agent CLI availability
springfield plan # Compile a work request into a runnable batch
springfield plans # Manage the registered plan-unit registry
springfield start # Execute the active batch from its saved cursor
springfield status # Inspect the active batch or work
springfield recover # Recover from a failed plan or orphaned batch
springfield version # Print build version
Supported agents (all fully executable):
--agents ...,gemini or by adding "gemini" to agent_priority; set GEMINI_API_KEY or sign in to the Gemini CLI before running headless)Springfield ships as two pieces: the CLI (the springfield binary that does all the work) and a plugin (the skills/slash-commands your agent runs). Install both.
brew install brentguistwite/tap/springfield
springfield version
brew upgrade springfield is the one upgrade you normally think about — new features land in the CLI and arrive here. Linux/Windows: install via Alternate Install Paths.
Claude Code:
/plugin marketplace add brentguistwite/springfield
/plugin install springfield@brentguistwite
Slash commands available after install: /springfield:plan, /springfield:plan-from-jira, /springfield:status, /springfield:recover. To execute a batch, run springfield start in a terminal. (For the Codex plugin, see Codex Plugin Directory.)
The plugin is a thin, stable shim over the CLI verbs (plan, start, status, recover), so it changes rarely. Plugin updates are manual on both platforms — run them only if a skill tells you to:
/plugin marketplace update springfield, then /plugin install springfield@brentguistwitecodex plugin marketplace upgrade brentguistwitenpx claudepluginhub brentguistwite/springfield --plugin springfield11 agents, 35 skills, 18 commands, 9 hooks — spec-driven multi-agent orchestration for Claude Code, with optional cross-device semantic memory.
Context-Driven Development plugin that transforms Claude Code into a project management tool with structured workflow: Context → Spec & Plan → Implement
Project discovery, planning, and quality analysis system with parallel agents
Compound Engineering workflow: PRD-driven sprints, isolated worktrees, hook-enforced safety, automated learning. Skills become /vini-workflow:plan, /vini-workflow:compound, etc.
Plan and autonomously build a software task end-to-end. Recons the codebase, applies preloaded memory, decomposes into the right number of phases, gets one confirmation, then prepares a single ready-to-paste /goal command — one paste between you and done — that drives execution to completion with built-in retry, fix-spec recovery, and per-phase memory writeback. Works on Claude Code and Codex.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses