transformers

A Claude Code plugin that gives you a full engineering team — not a smarter autocomplete.

14 specialized agents. 2 orchestrators. Every feature goes through requirements, planning, parallel execution, code review, and multi-angle testing. Not because it's fancy. Because that's how good software gets built.

---

⚔️ The Premise

Every line of code is a battle.

The Autobots build. They plan, research, write, and review. They care about correctness, performance, and craft.

The Decepticons attack. The moment Autobots ship, Megatron deploys his testers from every angle — unit, integration, end-to-end, security. Their mission is to find what the Autobots missed. They have no loyalty to the code. They want it to fail.

If the Decepticons find nothing — the code ships. If they find something — it goes back to the Autobots.

The goal is for the Autobots to win. But they only win by building something the Decepticons can't break.

That's not a metaphor. That's the actual development cycle.

---

The Problem

Claude Code is powerful. But raw power without structure is just speed in the wrong direction.

Most developers use 20% of what Claude Code can do. Single prompts, single context, no process, no memory. Transformers is how you use the other 80% — consistent workflows, specialist agents working in parallel, decisions that persist across sessions.

The same Claude. A proper system around it.

---

What You Actually Get

A real development cycle — not a chat.

Every feature starts with requirements and a definition of done. Every plan gets your approval before a single line is written. Every build goes through code review and testing before it's called done. You stay the architect. The agents do the work.

Specialists, not a generalist wearing hats.

Bumblebee thinks about users. Ironhide thinks about performance. Ratchet thinks about data integrity. Barricade thinks like an attacker. The same Claude model, trained to think differently — because different problems need different instincts.

Parallel execution that actually works.

Independent tasks run simultaneously across multiple agents. Optimus decomposes the work, identifies what can run in parallel, and coordinates the results. What would take 10 sequential steps takes 3.

Memory that survives.

Agents accumulate decision rules per project across sessions. "Always pull before push here — CI auto-bumps versions." "Skip Barricade for pure UI changes." The plugin gets smarter the more you use it. Other tools forget everything when the context resets.

Git handled properly.

GitMaster owns all things git — worktrees for isolation, branching strategy, rebase vs merge decisions, conflict resolution, PR review. Not an afterthought. A specialist.

Work that survives context limits.

Every phase writes to artifact files. If Claude Code compacts or you close the terminal, nothing is lost. Resume exactly where you left off.

---

Quick Start

# Install (one-time)
/plugin marketplace add ShankarKakumani/transformers
/plugin install transformers@transformers

# Initialize your project (run once per repo)
/transformers:init

# Build a feature — full lifecycle
optimus, build a search bar with filters

# Fix a bug — gather, investigate, fix, verify
optimus, bugfix login fails after password reset

# Test from every angle
megatron, test the auth flow

# Git operations
gitmaster, review this PR
gitmaster, set up worktrees for the payment feature

---

Commands

Lifecycle Commands

Full development cycle. Artifact tracking, approval gates, persistent state, resumable after compaction.

Command	What it does
/transformers:feature	Requirements → research → plan → build → review → test
/transformers:bugfix	Gather → investigate → fix plan → fix → verify

Standalone Commands

Use independently or alongside lifecycle work.