Spec4 is a structured pipeline of seven AI agents. Each one handles a distinct phase of project planning — from vision to AI features to executable phases — produces a machine-readable output, and hands it forward to the next. You stay in control at every step.
Spec4 is a local app — it runs on your machine, and your code and keys never leave it. With Python 3.12+ and uv installed:
Spec4 opens in your browser at localhost:8050. The first thing you'll do is set up your session:
.spec4/ folder inside it — versioned, portable, and yours.
Once configured, you move through the pipeline. You can start from scratch with a new idea, begin with CodeScanner if you're planning changes to an existing project, or jump in at any agent — Spec4 tracks what each one needs.
If you're building something new from scratch, you can skip straight to Brainstormer. But if you're extending or redesigning an existing project, CodeScanner reads your codebase and produces a structured analysis before any planning begins.
It walks through six areas — project type, architecture, languages and frameworks, build system, coding style, and notable observations — and asks you to confirm or correct each one. The result travels with the spec through every downstream agent.
code_review.json
Brainstormer is a collaborative agent that asks you one focused question at a time. It surfaces assumptions, identifies gaps, and pushes back when something is unclear — without overwhelming you with a form to fill out.
Each answer adds to a running vision statement you can review and revise at any step. Alongside it, Brainstormer writes a behavioral spec for every feature — purpose, inputs, outputs, success criteria, failure modes — so downstream agents work from specifics, not summaries. Brainstormer deliberately stays in its lane: it won't ask about technology, hosting, or libraries. The focus is entirely on what you're building, who it's for, and why it matters.
vision.json + feature_specs.json
Agentifier reads your vision and feature specs and surfaces every place AI can genuinely help. You choose how ambitious to be in an interactive selection panel — Agentifier keeps the selection consistent, automatically pulling in anything your choices depend on.
Each selected capability is placed on a nine-tier complexity ladder — from plain deterministic code up through RAG, tool agents, and multi-agent collaboration — and specced in full: inputs, outputs, mechanisms, evals, and failure modes, prioritized into steel thread, MVP, and later. In a hurry? ⏩ Fast Forward sweeps the remaining decisions with Agentifier's best recommendations, then presents the complete set for your review.
ai_features.json
Designer reads your vision statement and generates a self-contained HTML mock of your application's look and feel — no frameworks, no build step, no external dependencies. Open it in any browser, share it with stakeholders, or hand it to your coding agent as a visual spec.
Designer plans before it draws: it first writes a structured design manifest tying every screen element back to your features — including your AI features, rendered as real in-context interactions — then generates the mock from the plan. Iterative refinement is built in: describe what to change and it regenerates, guided by screenshots or reference images you like or dislike. Designer runs in parallel — start it any time after Brainstormer — and it's skipped automatically for CLI and terminal projects.
design/mock.html + design/manifest.json
StackAdvisor takes your vision, your AI feature specs, and your UI mock if Designer ran, and walks you through every layer of the technology decision: programming language, deployment platforms, hosting approach, libraries for each functional area, and coding style. Agentifier's tier choices shape the recommendations — a RAG feature brings a vector store into the conversation, a tool agent brings a tool harness.
For each choice, it presents ranked options with honest trade-off analysis — maintenance status, adoption, footprint, what you'd have to write yourself without it. When a code review is present, it actively flags conflicts between what you have and what you're considering. ⏩ Fast Forward is available whenever you'd rather review a complete recommendation than decide topic by topic.
stack.json
Phaser takes the vision, AI feature specs, stack spec, and design mock and produces a numbered sequence of implementation phases — one self-contained Markdown file per phase, with a summary, dependency list, configuration requirements, step-by-step instructions, a risk assessment, and an exact verification command. Your AI features are placed explicitly, steel-thread capabilities first.
Phase 1 is always a Steel Thread — the minimal end-to-end connection that proves your stack is wired together before any feature development begins. If a phase would require a dependency not in your stack spec, Phaser stops and asks for your approval first. ⏩ Fast Forward is here too when you want the full plan drafted for review in one sweep.
phases/phase<N>.md (downloadable as phases.zip)
Deployer works in two parts. First, you tell it which AI coding agent you'll use (Claude Code, Hermes, Kiro, Antigravity, and others are supported). Deployer searches for current documentation on that agent and gives you precise guidance for loading and executing Spec4 phases — exact syntax, recommended workflow, and known pitfalls.
Second, Deployer walks through your deployment strategy one question at a time: target platform, containerization, CI/CD pipeline, environment configuration, monitoring — and the AI channel: keys, observability, evals, and cost controls in production. For cloud deployments, it can generate complete Terraform infrastructure scripts, and on new projects it writes your repository's README. ⏩ Fast Forward is available here as well.
deployment-plan.md + project README.md
A real product isn't planned once — it's planned in rounds. Every Spec4 planning round is self-contained in a versioned folder: .spec4/v0/, then v1/, then v2/. When your coding agent finishes the last phase of a round, it marks the round implemented — and the next Spec4 session opens a fresh round, starting with a new CodeScanner pass so planning always builds on what actually got built.
Inside a round, the Agents page keeps every artifact honest. Each agent shows its state at a glance — Start, Modify, Needs Update, Required, or Not Ready — driven by the dependency graph between artifacts. Revise your vision, and Spec4 flags exactly which downstream specs need another look. Nothing goes silently stale.
Spec4 doesn't lock you into an agentic coding tool or a deployment workflow. The output is structured JSON, Markdown phases, a deployment plan, and a UI mock — all yours to use however you like. Hand a phase to Claude Code, deploy to your own infrastructure, design on your own schedule.