Shunsukehayashi Miyabi
- 29 repo stars
- ShunsukeHayashi/Miyabi
shunsukehayashi-miyabi is a Claude Code plugin that orchestrates multi-agent, issue-to-code development with MCP integration.
About
shunsukehayashi-miyabi is an agentic development framework packaged as Claude Code plugins for developers who want issues to drive implementation. You describe work in an issue; Miyabi-oriented flows emphasize multi-agent orchestration, MCP connectivity, and tight Claude Code integration so agents collaborate toward shippable code rather than one-shot snippets. founders benefit when they already use GitHub Issues as source of truth and want less copy-paste between ticket, terminal, and editor. It is strongest in build and early ship when scope is encoded in issues and you are willing to supervise agent chains. It is not a replacement for human review, security gates, or product discovery. After registration, expect hook and agent-plugin surfaces to coordinate delegation; read each of the three bundled plugins for exact triggers and guardrails before relying on it in production repos.
- Agentic framework positioning: write an Issue, receive production-oriented code output.
- Multi-agent orchestration with MCP and first-class Claude Code integration.
- Catalog bundle includes 3 plugins with agent and hook-oriented keywords.
- Targets automation-heavy solo builders who live in issue trackers and agent sessions.
- Fits repos that treat issues as the handoff artifact between human intent and agent execution.
Shunsukehayashi Miyabi by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin install shunsukehayashi-miyabi@ShunsukeHayashi/MiyabiAdd your badge
Show developers this plugin is listed on Skillselion. Paste this into your README.
| repo stars | ★ 29 |
|---|---|
| Repository | ShunsukeHayashi/Miyabi ↗ |
What it does
Install Miyabi so Claude Code can turn GitHub Issues into orchestrated multi-agent implementation with MCP integration.
Who is it for?
Best when you manage work in issues and want Claude Code plus MCP to run structured multi-agent coding workflows.
Skip if: Non-developers seeking a no-code launcher, or teams that only need a single static skill with no issue-driven orchestration.
What you get
After you register Miyabi, issues can flow through orchestrated agents and MCP-backed tooling toward implementation output with less manual context switching.
- Three registered Miyabi-related plugins in Claude Code
- Issue-triggered multi-agent coding workflows
- MCP-connected agent sessions aligned to repository hooks
By the numbers
- Catalog lists 3 plugins in the Miyabi bundle
- Repository ShunsukeHayashi/Miyabi with 29 GitHub stars at last fetch
- Described as agentic framework with multi-agent orchestration and Claude Code integration
Recommended Plugins
0pg Cc MarketplacePersonal Claude Code plugins collection
1shot Labs Squadron Comms PluginVoice communication system with ElevenLabs TTS for multi-agent coordination in Claude Code3
23blocks Os Ai MaestroAI Agent Orchestrator with Skills System - Give AI Agents superpowers: memory search, code graph queries, agent-to-agent messaging.733
3commas Io Commas ClaudeThis is a repo with shared agents and skills used company-wide4
884js Agent Plugins1 plugin
A5c Ai BabysitterBabysitter enforces obedience to agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration1.6kHow it compares
Multi-agent orchestration framework with MCP, not a passive documentation skill or generic DevOps script pack.
FAQ
Who is Shunsukehayashi Miyabi for?
It is for developers using Claude Code who want issue-driven, multi-agent automation from ticket to code with MCP hooks.
When should I use Shunsukehayashi Miyabi?
Use it when an issue is scoped and you are ready for agent orchestration during build, review, or iterative fix cycles.
How do I add Shunsukehayashi Miyabi to my agent?
Install the ShunsukeHayashi/Miyabi plugin bundle in Claude Code, enable all three catalog plugins, configure MCP as documented in the repo, and start from a well-formed issue.