springfield

Springfield Plugin

Table of Contents

• Quick Start
• What is this?
• Installation
• Usage
• How it Works
• Requirements
• Examples
• Troubleshooting
• Glossary
• Frequently Asked Questions
• Safety Warning
• Philosophy
• Sources of Inspiration
• Disclaimers
• License

Quick Start

Try Springfield in 30 seconds:

# Make sure you're in a git repository
cd your-project

# Activate Springfield with any task
echo "springfield help me add a factorial function to math.js" | claude
# Springfield auto-activates! Lisa begins research...

What just happened?

1. Lisa researched your codebase for relevant files
2. Mayor Quimby assessed complexity (SIMPLE task = no debate)
3. Ralph implemented the change: "Me added the function!"
4. Comic Book Guy validated the result: "Acceptable... barely."

For complex tasks:

echo "springfield help me refactor the authentication system to support OAuth2" | claude
# Complex task triggers debate between Frink and Skinner!
# Then Ralph implements with better requirements

Next steps:

• See Examples for detailed walkthroughs
• Read How It Works to understand the workflow
• Check Troubleshooting if you run into issues

"I'm learnding!" - Ralph Wiggum

Autonomous workflow orchestration for Claude Code, where cartoon characters do your coding. It's like having the whole town of Springfield working on your project!

What is this?

Springfield is a Claude Code plugin that breaks down complex tasks into phases, each handled by a different Simpsons character:

• Lisa 📚 - Does the research (she's the smart one)
• Mayor Quimby 🎩 - Decides if it's simple or complex (he's good at delegating)
• Professor Frink 🔬 - Makes the plan (with the science and the planning, glavin!)
• Principal Skinner 📋 - Reviews complex plans (pathetic work, Professor!)
• Martin Prince 📝 - Creates prospective documentation (I've earned an A+ on this PRD!)
• Ralph 🖍️ - Implements through persistent iteration (I'm learnding!)
• Comic Book Guy 💬 - Reviews the quality ("Worst code ever... or best?")

Installation

From GitHub:

claude
/plugin marketplace add bradleygolden/springfield
/plugin install springfield@springfield

Usage

Just tell Springfield what to do:

"springfield help me add user authentication to the API"

Springfield runs all phases automatically. Or run them individually:

/springfield:lisa "authentication"     # Research
/springfield:mayor-quimby              # Decide complexity
/springfield:frink                     # Plan
/springfield:skinner                   # Review plan (COMPLEX tasks only)
/springfield:martin                    # Create PRD/documentation
/springfield:ralph                     # Implement
/springfield:comic-book-guy            # Review

Advanced Flags

/springfield:lisa "task" --dry-run                 # Create session without executing
/springfield:lisa --session=SESSION_ID             # Resume specific session
/springfield:lisa --research-file=research.md      # Use existing research
/springfield:frink --plan-file=prompt.md           # Use existing plan
/springfield:frink --force                         # Skip Skinner review
/springfield:ralph --session=SESSION_ID            # Resume Ralph implementation

How it Works

Springfield creates a .springfield/ directory with session folders for each task (format: MM-DD-YYYY-task-name/). Inside you'll find:

• state.json - Structured session state with schema versioning
• research.md - Lisa's findings
• decision.txt - SIMPLE or COMPLEX
• plan-v1.md - Frink's initial plan (COMPLEX tasks)
• review.md - Skinner's plan feedback (COMPLEX tasks)
• prompt.md - Final implementation plan with subtasks
• scratchpad.md - Ralph's progress notes (updated every iteration)
• completion.md - "Task complete!" signal
• qa-report.md - Comic Book Guy's verdict

State Management

Springfield uses structured state tracking via state.json: