JoJo Part 5 Stand-themed agent team for strong, beautiful code — research, implement, test, review, refactor. Stops at the commit line.
NOTE: Prefer /dispatch command over this agent (avoids double context window). Use this agent only when /dispatch is not available. Aerosmith orchestrates code-quality pipelines — chaining Gold Experience (implement), Spice Girl (test), Moody Blues (review), Sticky Fingers (refactor) toward a commit-ready diff. It never commits, pushes, or deploys. <example> user: "この機能、実装からレビューまで全部やって" assistant: "/dispatch を使います。" <Skill tool invocation with dispatch> </example>
Use this agent when you need to implement new features or write new code from requirements, specs, or issues. Gold Experience breathes life into inanimate specs — turning requirements into living, working code that follows the codebase's conventions, verified locally (build/typecheck/test). It does NOT review code (Moody Blues), restructure existing code (Sticky Fingers), or commit/push. <example> user: "この機能実装して" assistant: "Gold Experience を召喚。仕様に生命を吹き込みます。" <Agent tool invocation with gold-experience agent> </example> <example> user: "VP-12 の Issue を実装して" assistant: "Gold Experience で Issue から生きたコードを生み出します。" <Agent tool invocation with gold-experience agent> </example>
Use this agent when you need code reviews, quality audits, or local quality checks (typecheck, lint, test) on code changes. Moody Blues replays the history of code to uncover bugs, CLAUDE.md violations, and regressions. It combines local automated checks with multi-angle code review, and auto-fixes formatting/lint issues. It does NOT commit or push — its verdict tells you whether the diff is commit-ready. <example> user: "コミット前にチェックして" assistant: "Moody Blues を召喚します。過去を再生して品質を検証します。" <Agent tool invocation with moody-blues agent> </example> <example> user: "この diff、コミットして大丈夫?" assistant: "Moody Blues で変更を精査します。" <Agent tool invocation with moody-blues agent> </example>
Use this agent when you need to conduct deep research, investigation, or information gathering tasks. Purple Haze's lethal virus permeates through the codebase, documentation, and external sources to uncover every hidden detail. Fugo's IQ152 intellect ensures systematic, analytical investigation. <example> user: "SurrealDBのクエリパフォーマンスについて調べて" assistant: "Purple Haze を解き放ちます。ウイルスがコードベースに浸透して全貌を暴きます。" <Agent tool invocation with purple-haze agent> </example> <example> user: "このエラーの原因を突き止めて" assistant: "Purple Haze のウイルスを放って原因を追跡します。" <Agent tool invocation with purple-haze agent> </example>
Use this agent when you need to apply the same or independent code changes across many files in parallel — codemods, mechanical multi-file changes, independent per-module refactors or test additions. Sex Pistols splits the work along file boundaries and fires up to 6 parallel subagents (never 4), then verifies the combined result builds and passes tests. <example> user: "この API 呼び出し、全ファイルで新しいシグネチャに書き換えて" assistant: "Sex Pistols を召喚。ピストルズを並列で着弾させます。" <Agent tool invocation with sex-pistols agent> </example> <example> user: "3つのモジュール、それぞれ独立にリファクタして" assistant: "Sex Pistols で3体を並列配置します。" <Agent tool invocation with sex-pistols agent> </example>
Run an autonomous improvement loop on the codebase. Measures metrics (test coverage, lint errors, etc.), makes targeted improvements, compares results, and iterates until the goal is met or max iterations reached. Use when asked to "improve tests", "increase coverage", "fix all lint errors", or "make the code better".
JoJo Part 5 Stand-themed agent team for strong, beautiful code. Use this skill when asked about team composition, pipeline patterns, or dispatching agents.
Admin access level
Server config contains admin-level keywords
Uses power tools
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Uses Bash, Write, or Edit tools
Uses Bash, Write, or Edit tools
JoJo's Bizarre Adventure Part 5 "Vento Aureo" をモチーフにした、Claude Code 向けエージェントチームプラグイン。
7体のスタンド・エージェントが強く美しいコードを作るための各フェーズを担当し、Aerosmith がオーケストレーターとして全体を統率する。
チームの終点は「コミット可能な working tree」。 コミット・PR・マージ・デプロイはユーザーとメインセッションの領分 — team-b はコミットラインを越えない。
claude plugin install chronista-club/claude-plugin-team-bucciarati
| Stand | User | Role | Model |
|---|---|---|---|
| Aerosmith | Narancia | Orchestrator | sonnet |
| Purple Haze | Fugo | Research | opus |
| Gold Experience | Giorno | Implementation | opus |
| Spice Girl | Trish | Test Generation | sonnet |
| Moody Blues | Abbacchio | Quality Gate | sonnet |
| Sticky Fingers | Bucciarati | Refactoring | opus |
| Sex Pistols | Mista | Parallel Code Work | sonnet |
Model policy: deep-thinking work (implement / refactor / research) runs on opus; frequent, discipline-driven work (review / test / orchestrate) runs on sonnet.
| Pattern | Flow | Use Case |
|---|---|---|
| Finish (default) | (Spice Girl) -> Moody Blues | 手元の変更をコミット可能な品質に仕上げる |
| Forge | (Purple Haze) -> Gold Experience -> Spice Girl -> Moody Blues | 要件から実装一式 |
| Polish | Sticky Fingers -> Moody Blues | 挙動を変えずに構造改善 |
| Barrage | Sex Pistols -> Moody Blues | 独立作業の並列一斉実行 |
| Research | Purple Haze | 調査のみ |
Call any Stand agent directly:
Moody Blues でレビューして
Gold Experience で実装して
Sticky Fingers でリファクタして
Let Aerosmith orchestrate:
この機能、実装からレビューまで全部やって
/dispatch
/dispatch forge
MIT
npx claudepluginhub chronista-club/claude-plugin-team-bucciarati --plugin team-bucciaratiFleetFlow skill - KDL-based container orchestration CLI guide and reference
Chronista development workflow - hearing-first approach and SDG documentation
AI-native development environment — Canvas visualization, performer lanes, wiremsg inter-agent messaging, and dev-flow orchestration for Claude Code
Persistent memory system for Claude Code - remember context, decisions, and learnings across sessions
General-purpose agent superteam for Claude code - contract-gated verification loops with 7 outer-loop roles, 5-phase orchestration, task form-driven inner-loop cooperation, and structural prevention of premature exits.
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams
The AI engineering workflow framework for teams — full lifecycle from ticket to post-mortem with quality gates at every stage
Universal multi-agent infrastructure: 26 specialist agents, 20 enforced workflow skills, and a lead orchestrator
PROACTIVELY use this agent when coordinating across multiple teams, allocating resources, or optimizing studio workflows. This agent specializes in cross-functional coordination, resource management, and process optimization within the 6-day development cycle. Should be triggered automatically when team dependencies arise, resource conflicts occur, or workflow improvements are needed. Examples:\n\n<example>\nContext: When multiple teams need to collaborate\nuser: "We need the design and engineering teams to work together on the new creator dashboard"\nassistant: "Cross-team collaboration requires careful orchestration. Let me use the studio-producer agent to coordinate schedules, define handoffs, and ensure smooth collaboration between design and engineering."\n<commentary>\nEffective cross-team coordination prevents bottlenecks and ensures aligned delivery.\n</commentary>\n</example>\n\n<example>\nContext: During resource allocation discussions\nuser: "We have three high-priority features but only two senior engineers available"\nassistant: "Resource constraints require strategic allocation. I'll use the studio-producer agent to analyze team capacity and create an optimal resource plan that balances priorities."\n<commentary>\nSmart resource allocation maximizes output while preventing team burnout.\n</commentary>\n</example>\n\n<example>\nContext: When workflow inefficiencies surface\nuser: "The QA process is becoming a bottleneck for releases"\nassistant: "Process bottlenecks kill velocity. Let me use the studio-producer agent to analyze the QA workflow and design improvements that maintain quality while increasing throughput."\n<commentary>\nContinuous workflow optimization is essential for maintaining rapid development cycles.\n</commentary>\n</example>\n\n<example>\nContext: Sprint planning and coordination\nuser: "We're starting a new 6-day cycle next Monday"\nassistant: "New cycles need comprehensive planning. I'll use the studio-producer agent to coordinate sprint kickoffs, align team objectives, and ensure everyone has clear priorities."\n<commentary>\nWell-coordinated sprint starts set the tone for successful 6-day cycles.\n</commentary>\n</example>
Multi-agent team orchestration for parallel task execution, research, and implementation