Claude Code writes code fast. It's worse at writing the code your team would actually ship — code that follows your conventions, has tests you trust, and survives review.
Squid is a Claude Code plugin that turns a feature spec into a reviewed PR through a 5-agent pipeline — PA → SWE → Tester → PR Reviewer → On-Call — with exactly two human gates: plan approval and final merge. No file templates, no render step: just markdown specs and agent contracts, and every file in your project gets written by an agent that reads them.
How it works
Run /squid-plan <feature-spec> then /squid-implement-night, and Squid drives this end-to-end:
feature spec
│
▼ /squid-plan
┌──────────────────────────────────────────────────────────────┐
│ grill → PA grooms Tasks Plan (+ADR) → HUMAN approves (1/2) │
│ → branch + worktree │
└──────────────────────────────────────────────────────────────┘
│ /squid-implement-night (runs end-to-end in the worktree)
▼
┌──────────────────────┐ ┌───────────────────┐ ┌─────────────────┐
│ /squid-implement-task│──▶ │ /squid-review │──▶ │ /squid-review-ci│
│ SWE ↔ Tester │ │ push → PA accept →│ │ On-Call drives │
│ commit each task │ │ PR-Reviewer │ │ CI to green │
└──────────────────────┘ └───────────────────┘ └─────────────────┘
│
▼
HUMAN squash-merges (2/2)
For a quick single change, run /squid-implement-task <task> (the same SWE ↔ Tester loop, no planning or review pipeline). Starting from an empty repo? Run /squid-scaffold first (see Quick start).
Who this is for
- Yes: solo devs and small teams shipping Python backends, TypeScript frontends, or Go TUIs who want Claude Code to consistently hit your team's bar without re-explaining conventions every session.
- Maybe not: teams with an established in-house agent pipeline they don't want to displace, or stacks Squid doesn't cover yet (Rust, Java, mobile — PRs welcome).
Learn How to Build Agentic Coding Frameworks From Scratch
Join 40k+ engineers subscribed to the Decoding AI Magazine to learn to build agentic coding frameworks like Squid from scratch.

Install
/plugin marketplace add iusztinpaul/squid
/plugin install squid@iusztinpaul
That's it. Open any repo in Claude Code; the agents and skills appear in /agents and /help. Run /plugin marketplace update iusztinpaul later to pull fresh changes.
Per-project install — auto-prompt for everyone who clones a specific repo
Commit this into the target repo's .claude/settings.json:
{
"extraKnownMarketplaces": {
"iusztinpaul": {
"source": {
"source": "github",
"repo": "iusztinpaul/squid"
}
}
},
"enabledPlugins": {
"squid@iusztinpaul": true
}
}
When a teammate (or future-you on a fresh machine) opens that repo and trusts the folder, Claude Code prompts them to add the marketplace and install in one step. enabledPlugins alone isn't enough — extraKnownMarketplaces is what tells Claude Code where squid@iusztinpaul resolves to.
Local plugin development — test uncommitted changes to Squid itself
claude --plugin-dir /path/to/squid
Launches Claude Code with the plugin loaded for the session. No marketplace, no install, no cache. Re-run after edits. This is the only path that exercises your local working tree directly on Claude Code v2.1+.
No comments yet.