Duck Soup
A structured development workflow for Claude Code with a team of specialized agents.
Overview
Four stooges in a trench coat posing as your dev team? Why, that's the oldest gag in software!
You got Groucho telling you where to put the code, Chico checking if you actually put it there, Zeppo making sure it doesn't explode the moment you turn your back, and Harpo... well, somebody's gotta write the docs, might as well be the one who never talks.
It's a structured workflow, which in Hollywood means you fire everyone in the right order!
— Groucho, your new technical architect
Installation
In Claude Code:
/plugin marketplace add schuyler/duck-soup
/plugin install dev
Usage
Start the development workflow with:
/dev:start <task description>
Example:
/dev:start Add user authentication with JWT tokens
The /dev:start command runs a structured workflow starting with requirements gathering and continuing through documentation and feedback. To resume an interrupted session, mention the session slug (e.g., "continue session-resumption").
Your All-Star Development Team
Four specialized agents:
Groucho (Project Architect)
- Checks for existing patterns in codebase
- Reviews architectural decisions
- Recommends solutions that match project conventions
Chico (Code Reviewer)
- Reviews completed implementations
- Verifies requirements adherence
- Identifies issues
Zeppo (Debugging Specialist)
- Investigates errors and unexpected behavior
- Provides testing plans
Harpo (Documentation Specialist)
- Creates and updates project documentation
- Updates README, API docs, changelogs
Workflow Phases
The workflow consists of 7 sequential phases:
1. GATHER REQUIREMENTS
- Ask clarifying questions
- Confirm understanding
- Document requirements in
.claude/REQUIREMENTS.md
2. PLAN
- Consult Groucho for architectural guidance
- Create detailed implementation plan
- Document plan in
.claude/PLAN.md
- Get user confirmation before proceeding
3. IMPLEMENT
- Step-by-step execution (max 50 lines per step)
- User confirmation after each step
- One logical unit per step (one function, one file section, etc.)
4. REVIEW
- Consult Chico for code review
- Fix identified issues
- Verify adherence to requirements
5. VERIFY
- Consult Zeppo for testing guidance
- Execute verification steps
- Ensure implementation works correctly
- Document testing plan in
.claude/TESTING.md
6. DOCUMENT
- Consult Harpo for documentation
- Update relevant docs (README, API docs, etc.)
7. REFLECT
- Record session learnings
- Identify instruction gaps
- Document patterns discovered
Local Installation (for testing/development)
/plugin marketplace add /path/to/local/duck-soup
/plugin install dev
License
BSD 3-Clause License - see LICENSE for details.
Author
Schuyler Erle schuyler@nocat.net
schuyler