gregorydickson/pickle-rick-claude

<img src="images/pickle-rick.png" alt="Pickle Rick for Claude Code" width="100%" />

🥒 Pickle Rick for Claude Code

"Wubba Lubba Dub Dub! 🥒 I'm not just an AI assistant, Morty — I'm an autonomous engineering machine trapped in a pickle jar!"

Pickle Rick is a complete agentic engineering toolbelt built on the Ralph Wiggum loop and ideas from Andrej Karpathy's AutoResearch project. Hand it a PRD — or let it draft one — and it decomposes work into tickets, spawns isolated worker subprocesses, and drives each through a full research → plan → implement → verify → review → simplify lifecycle without human intervention.

New to PRDs? See the PRD Writing Guide for developers or the Product Manager's Guide for PMs defining and refining requirements. For internals, see Internals. For what's coming next, see the Feature Roadmap.

Recently released — /citadel conformance audit · v1.58 Convergence Toolchain Gates (details) · v1.57 /cronenberg meta-router · v1.56 pipeline resume hardening · v1.55 Agent Teams mode (/pickle-tmux --teams) · v1.51 Codex backend (--backend codex).

---

How to Build Things with Pickle Rick

Two ways to drive every step: just describe what you want (Rick routes to the right skill) or invoke the slash command yourself (explicit control). Same artifacts either way.

Fire and forget — for one-shot autopilot from goal to shipped code, hand the whole thing to /pickle-pipeline "<goal>" (build → citadel → anatomy-park → szechuan-sauce, sequential, with auto-refine when prose triggers it) or /cronenberg "<goal>" (meta-router that picks the right metaphor + cleanup chain for the task). Skip the step-by-step below.

Step 1: Write a PRD

Every feature starts with a PRD. Just describe what you want:

"Help me write a PRD fo