Claude Code plugin for development workflows that don't fall apart in long sessions.
Superpowers is great. Skill-based workflows, iterative spec review, subagent-driven development — all genuinely good ideas that I used for a long time. But some patterns kept showing up that I wanted to fix:
Agents get confident in their own prior reasoning. If you review code, fix stuff, then review again — the second pass comes back suspiciously clean. The agent's own reasoning from the first review is right there in context, and it can't really fathom that it missed something when its own thoughts are telling it everything was fine. Meridian isolates review subagents so the orchestrator only ever sees defects and a verdict, not the reviewer's internal reasoning.
They trust their training data way too much. Confidently writing code against APIs that have changed, using library features that don't work the way they remember — then wasting ages debugging when a quick docs check would've caught it upfront. Meridian verifies external APIs against live documentation before writing code.
Skill systems can be too rigid. Not everything needs the full brainstorm -> plan -> execute pipeline. Changing a button color shouldn't require a design spec. Meridian uses judgment about what warrants ceremony and what just needs doing.
Agents commit stuff you didn't ask for. Spec files staged automatically, AI attribution in every message, design docs forced past your gitignore. Meridian doesn't commit anything without asking, doesn't stage spec files, and doesn't put "Co-Authored-By: Claude" in your commits.
They don't push back enough. If you ask for something that'll cause problems, the agent should say so — with evidence and actual alternatives, each with an honest case made for it. And once you've picked a direction, it should go all in, not half-ass it and relitigate in review.
Hard-won knowledge dies with the session. You debug something for two hours, nail the root cause, and next session the agent suggests the exact approach you already ruled out. Meridian has a documentation skill for capturing gotchas, debugging context, and "we already tried this" notes so future sessions don't start from scratch.
| Skill | Does |
|---|---|
research |
Verify APIs/libs against live docs before implementing |
brainstorm |
Design exploration -> spec through conversation |
execute |
Implement from spec with verification gates |
delegate |
Dispatch subagents with clean context isolation |
debug |
Root-cause investigation, no fixes without understanding |
review |
Code review via isolated subagent |
respond |
Evaluate review feedback before acting on it |
commit |
Clean git commits, no AI attribution |
document |
Human-readable docs from resolved work |
/plugin marketplace add KodingDev/meridian
/plugin install meridian@meridian
Built on ideas from superpowers by Jesse Vincent — the skill-based workflow, subagent development, and iterative spec review all come from there. Meridian wouldn't exist without it.
Orchestration approach informed by Anthropic's context engineering research and the Claude Certification Guide.
MIT