production-grade
by nagisanzeninv5.2.0
Enhances Claude Code from producing raw code into delivering production-ready systems. 14 specialized agents handle architecture, tested code, security audit, CI/CD, and documentation. Use for building apps/websites/services, adding features, hardening, deployment, testing, review, or architecture design.
Keywords
production-gradesaasorchestratorfull-stackmeta-skillpipelinedevopsarchitecturetestingsecuritysreaimlllm
Documentation
# Production Grade Plugin for Claude Code
<p align="center">
<img src="assets/banner.png" alt="Meet the Production Grade crew — 14 AI agents" width="700">
</p>
<p align="center">
<a href="https://github.com/nagisanzenin/claude-code-production-grade-plugin"><img src="https://img.shields.io/github/stars/nagisanzenin/claude-code-production-grade-plugin?style=social" alt="GitHub stars"></a>
<img src="https://img.shields.io/badge/License-MIT-yellow.svg" alt="MIT License">
<img src="https://img.shields.io/badge/version-5.2.0-blue.svg" alt="Version">
<img src="https://img.shields.io/badge/agents-14-green.svg" alt="14 agents">
<img src="https://img.shields.io/badge/protocols-8-red.svg" alt="7 protocols">
<img src="https://img.shields.io/badge/execution%20modes-10-purple.svg" alt="10 modes">
</p>
<h3 align="center">14 AI agents, one install, idea to production.</h3>
```bash
/plugin marketplace add nagisanzenin/claude-code-plugins
/plugin install production-grade@nagisanzenin
```
<br>
## Built With This Plugin
| Project | Live | Description |
|---------|------|-------------|
| **PingBase** | [pingbasez.vercel.app](https://pingbasez.vercel.app/) | SaaS built end-to-end with the production-grade pipeline |
---
## Release Timeline
```
2026-03-07 v5.2 ●━━━ Frontend overhaul — functional-first, design polish, 4 visual style presets
│
2026-03-07 v5.1 ●━━━ Boundary Safety — 6 patterns for system boundary bugs, from real deployment
│
2026-03-06 v5.0 ●━━━ Verified & Resilient — receipt enforcement, re-anchoring, adversarial review
│
2026-03-06 v4.4 ●━━━ Freshness protocol — agents WebSearch to verify volatile data before implementing
│
2026-03-06 v4.3 ●━━━ Visual identity, pipeline dashboard, gate ceremonies
│
2026-03-06 v4.2 ●━━━ Adaptive routing, 10 execution modes, everyday SWE work
│
2026-03-05 v4.1 ●━━━ Engagement modes, scale-driven architecture, adaptive interviews
│
2026-03-04 v4.0 ●━━━ Two-wave parallelism, internal skill agents, dynamic task generation
│
2026-03-04 v3.3 ●━━━ Brownfield-safe — works on existing codebases
│
2026-03-03 v3.2 ●━━━ Auto-update, MECE intent routing, protocol crash fix
│
2026-03-02 v3.1 ●━━━ Polymath co-pilot — the 14th skill
│
2026-03-01 v3.0 ●━━━ Full rewrite — Teams/TaskList, 7 parallel points, shared protocols
│
2026-02-28 v2.0 ●━━━ 13 bundled skills, unified workspace, prescriptive UX
│
2026-02-24 v1.0 ●━━━ Initial release — autonomous DEFINE>BUILD>HARDEN>SHIP>SUSTAIN
```
---
## The Pipeline
```
YOU ──→ "Build a SaaS for ..."
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ DEFINE │
│ T1 Product Manager ─── BRD, user stories, acceptance criteria│
│ T2 Solution Architect ─ ADRs, API contracts, data models │
│ │
│ ┌─────────────┐ ┌──────────────┐ │
│ │ GATE 1 │ │ GATE 2 │ │
│ │ Requirements│ │ Architecture │ │
│ └─────────────┘ └──────────────┘ │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ BUILD + ANALYZE (Wave A — parallel) │
│ │
│ Backend ──── N agents (1 per service) QA ──── test plan │
│ Frontend ─── N agents (1 per page) Security ── STRIDE │
│ DevOps ──── Dockerfiles + CI skeleton Review ── checklist │
│ SRE ───── SLOs │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ HARDEN (Wave B — parallel against code) │
│ │
│ QA ─────── unit / integration / e2e / performance tests │
│ Security ── code audit + dependency scan (4 parallel phases) │
│ Review ──── arch / quality / performance (adversarial) │
│ DevOps ──── build + push containers │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ SHIP │
│ │
│ DevOps ── IaC + CI/CD ┐ │
│ Remediation ───────────┘ parallel ┌──────────────┐ │
│ SRE ── chaos + capacity ┐ │ GATE 3 │ │
│ Data Scientist ─────────┘ parallel │ Production │ │
│ │ Readiness │ │
│ └──────────────┘ │
└─────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────┐
│ SUSTAIN │
│ │
│ Technical Writer ── API ref + dev guides (parallel) │
│ Skill Maker ─────── 3-5 project-specific reusable skills │
│ Compound Learning ── pipeline insights for next run │
└─────────────────────────────────────────────────────────────────┘
│
▼
DONE ── receipts verified, agents cleaned up
```
> **3 gates. 2 waves. 10+ parallel execution points. ~3x faster than sequential.**
---
## 10 Execution Modes
Not just full builds. The orchestrator reads your request and routes automatically.
```
┌──────────────────────────────────────────────────────────────┐
│ │
│ Full Build ████████████████████████ all 14 agents │
│ Feature █████████████ PM+Arch+Eng+QA │
│ Harden ████████ Sec+QA+Review │
│ Ship ██████ DevOps+SRE+DS │
│ Architect ████ Solution Architect │
│ Test ███ QA Engineer │
│ Review ███ Code Reviewer │
│ Document ███ Technical Writer │
│ Optimize █████ SWE+Data Scientist │
│ Explore ███ Polymath │
│ │
└──────────────────────────────────────────────────────────────┘
```
```
"Build a SaaS for e-commerce" → Full Build
"Add Stripe billing to my API" → Feature
"Audit this codebase before launch" → Harden
"Set up CI/CD and monitoring" → Ship
"Review this PR for quality" → Review
"Help me think about a fintech app" → Explore
```
---
## The Crew
```
┌─────────────────┐
│ ORCHESTRATOR │
│ routes, gates, │
│ receipts │
└────────┬────────┘
│
┌────────────────────┼────────────────────┐
│ │ │
┌────▼─────┐ ┌───────▼────────┐ ┌──────▼───────┐
│ DEFINE │ │ BUILD │ │ HARDEN │
│ │ │ │ │ │
│ PM │ │ Software Eng │ │ QA Engineer │
│ Architect│ │ Frontend Eng │ │ Security Eng │
│ │ │ DevOps │ │ Code Review │
└──────────┘ └────────────────┘ └──────────────┘
│
┌────────────────────┼────────────────────┐
│ │ │
┌────▼─────┐ ┌───────▼────────┐ ┌──────▼───────┐
│ SHIP │ │ SUSTAIN │ │ ANYTIME │
│ │ │ │ │ │
│ DevOps │ │ Tech Writer │ │ Polymath │
│ SRE │ │ Skill Maker │ │ Data Sci │
└──────────┘ └────────────────┘ └──────────────┘
```
| # | Agent | Domain | Sole Authority |
|---|-------|--------|:-:|
| 1 | **Orchestrator** | Routes, gates, receipts, re-anchoring | |
| 2 | **Polymath** | Research, ideation, onboarding, translation | |
| 3 | **Product Manager** | BRD, user stories, acceptance criteria | Requirements |
| 4 | **Solution Architect** | ADRs, tech stack, API contracts, data models | Architecture |
| 5 | **Software Engineer** | Handlers, services, repositories, business logic | |
| 6 | **Frontend Engineer** | Design system, components, pages, accessibility | |
| 7 | **QA Engineer** | Unit, integration, e2e, performance tests | |
| 8 | **Security Engineer** | STRIDE, OWASP, PII, dependency scanning | Security |
| 9 | **Code Reviewer** | Architecture conformance, anti-patterns (adversarial) | Code Quality |
| 10 | **DevOps** | Docker, Terraform, CI/CD, containers | Infrastructure |
| 11 | **SRE** | SLOs, chaos engineering, runbooks, capacity | Reliability |
| 12 | **Data Scientist** | LLM optimization, prompt engineering, cost modeling | |
| 13 | **Technical Writer** | API reference, dev guides, architecture docs | |
| 14 | **Skill Maker** | Generates project-specific reusable Claude Code skills | |
---
## What Makes It Different
```
┌──────────────────────────────────────────────────────────────┐
│ │
│ RECEIPT ENFORCEMENT RE-ANCHORING │
│ ───────────────── ──────────── │
│ Every agent writes a Orchestrator re-reads specs │
│ JSON receipt as proof. FROM DISK at every phase │
│ No receipt = not done. transition. No context drift │
│ Gate won't open without in multi-hour runs. │
│ verified artifacts. │
│ │
│ ADVERSARIAL REVIEW FRESHNESS PROTOCOL │
│ ────────────────── ────────────────── │
│ Code reviewer assumes Agents detect volatile data │
│ code is WRONG until (model IDs, pricing, CVEs) │
│ proven right. Scales and WebSearch to verify │
│ from critical-only to BEFORE implementing. │
│ hostile break scenarios. │
│ │
│ CONSTRAINT-DRIVEN ARCH ZERO OPEN-ENDED QUESTIONS │
│ ───────────────────── ───────────────────────── │
│ Architecture derived from Every interaction is arrow │
│ YOUR scale, budget, team, keys + Enter. Polymath │
│ compliance — not templates. translates at every gate. │
│ 100 users → monolith. │
│ 10M users → microservices. │
│ │
└──────────────────────────────────────────────────────────────┘
```
---
## Protocol Stack
All 14 agents load the same 8 protocols at startup:
```
┌──────────────────────────────────────────────┐
│ Boundary Safety │ ← system boundary patterns
├──────────────────────────────────────────────┤
│ Receipt Protocol │ ← proof of completion
├──────────────────────────────────────────────┤
│ Freshness Protocol │ ← verify volatile data
├──────────────────────────────────────────────┤
│ Visual Identity │ ← consistent formatting
├──────────────────────────────────────────────┤
│ Conflict Resolution │ ← sole-authority domains
├──────────────────────────────────────────────┤
│ Tool Efficiency │ ← dedicated tools > shell
├──────────────────────────────────────────────┤
│ Input Validation │ ← classify external inputs
├──────────────────────────────────────────────┤
│ UX Protocol │ ← structured interactions
└──────────────────────────────────────────────┘
```
---
## Engagement Modes
Choose your depth at pipeline start. Propagates to all 14 agents.
```
Express ░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░ auto-derive, 2-3 questions
Standard ████░░░░░░░░░░░░░░░░░░░░░░░░░░ balanced, 3-5 questions
Thorough █████████████░░░░░░░░░░░░░░░░░░ deep discovery, 5-8 questions
Meticulous ██████████████████████████████░░ full control, 8-12 questions
```
---
## Token-Efficient Architecture
Large skills split into **router + on-demand phases**. Only what's needed loads. Independent phases run as parallel agents with minimal context.
```
Polymath ─────────── 6 modes onboard | research | ideate | advise | translate | synthesize
Software Engineer ── 5 phases context | implement | cross-cutting | integration | local dev
Frontend Engineer ── 6 phases analysis | functional foundation | components | pages | design polish | testing
Security Engineer ── 6 phases threat model | code audit | auth | data | supply chain | remediation
SRE ─────────────── 5 phases readiness | SLOs | chaos | incidents | capacity
Data Scientist ──── 6 phases audit | LLM optimization | experiments | pipeline | ML infra | cost
Technical Writer ── 4 phases audit | API reference | dev guides | Docusaurus
```
---
## By the Numbers
```
┌────────────────────────────────────────────────────┐
│ │
│ 14 specialized agents │
│ 8 shared protocols │
│ 10 execution modes │
│ 10+ parallel execution points │
│ 3 approval gates │
│ 4 engagement modes │
│ ~3x faster than sequential execution │
│ ~45% fewer input tokens from parallelism │
│ 0 open-ended questions — all structured │
│ 5 languages: TS, Go, Python, Rust, Java/Kotlin │
│ │
└────────────────────────────────────────────────────┘
```
---
## Installation
```bash
# Marketplace (recommended)
/plugin marketplace add nagisanzenin/claude-code-plugins
/plugin install production-grade@nagisanzenin
# Or from source
git clone https://github.com/nagisanzenin/claude-code-production-grade-plugin.git
claude --plugin-dir /path/to/claude-code-production-grade-plugin
```
**Requirements:** Claude Code (with plugin support), Docker & Docker Compose, Git.
Works on existing codebases — brownfield detection auto-maps your project structure.
---
## FAQ
**Does it write working code?** Yes. Write, build, test, debug, fix. No stubs. No TODOs.
**Existing projects?** Yes. Brownfield detection auto-maps. Run specific modes or full pipeline.
**How do I know it ran everything?** Receipts. JSON proof from every agent, verified at gates.
**Context degrade in long runs?** No. Re-anchoring re-reads from disk at every phase transition.
**Not technical?** Every interaction is multiple choice. Polymath translates at any gate.
---
## Contributing
1. Fork the repo
2. Create a branch: `git checkout -b feature/your-feature`
3. Commit changes
4. Open a Pull Request
**Adding a skill:** Create `skills/your-skill-name/SKILL.md` with `---` frontmatter.
---
## Star History
<a href="https://star-history.com/#nagisanzenin/claude-code-production-grade-plugin&Date">
<picture>
<source media="(prefers-color-scheme: dark)" srcset="https://api.star-history.com/svg?repos=nagisanzenin/claude-code-production-grade-plugin&type=Date&theme=dark" />
<source media="(prefers-color-scheme: light)" srcset="https://api.star-history.com/svg?repos=nagisanzenin/claude-code-production-grade-plugin&type=Date" />
<img alt="Star History Chart" src="https://api.star-history.com/svg?repos=nagisanzenin/claude-code-production-grade-plugin&type=Date" />
</picture>
</a>
---
## License
MIT
---
<p align="center">
<strong>14 agents. 8 protocols. 10 modes. One install.</strong>
</p>