epic
v0.1.0Development orchestrator: a planner decomposes a large Epic into PR-sized, dependency-ordered tasks, and multiple runners autonomously implement them in parallel git worktrees, coordinating through a filesystem-backed state machine.
By Masayoshi MizutaniLicense: Apache-2.00 GitHub starsUpdated 3 months ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Jun 27, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install epic for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install epic-3@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/m-mizutani/claude-codeClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/epic/.
Plugin files
├── .claude-plugin/plugin.json├── skills/plan/SKILL.md└── skills/run/SKILL.md
Included Skills2
Plan and decompose a large development Epic into a coherent overall design plus PR-sized, dependency-ordered tasks that multiple autonomous runners implement in parallel. Use this whenever the user wants to break a big feature/project/initiative into tasks, set up parallel or multi-agent development, orchestrate several Claude runners, define an epic, or says things like 'plan this epic', 'break this down into tasks', 'set up the epic', 'decompose this work', 'epic:plan', or hands you a large spec/PRD and wants it turned into an executable plan. This is the orchestrator's planning half and pairs with epic:run. Prefer this over ad-hoc task lists whenever the work is large enough to span multiple PRs or multiple workers.
Autonomously pick up and implement Epic tasks one at a time from inside a git worktree: claim a ready task, write a spec, get it auto-reviewed, implement it, open a PR, block until it is merged, then immediately take the next task — never stopping until every reachable task is done. Use whenever the user wants to run an epic, start or continue an epic runner, work epic tasks in parallel, join an epic as a worker, or says things like 'epic:run', 'run the epic', 'start a runner', 'take a task', 'work the epic'. This is the orchestrator's execution half and pairs with epic:plan. It MUST run inside a worktree and coordinates with other runners through the shared .epic/ state.
Plugin manifests1
{
"name": "epic",
"description": "Development orchestrator: a planner decomposes a large Epic into PR-sized, dependency-ordered tasks, and multiple runners autonomously implement them in parallel git worktrees, coordinating through a filesystem-backed state machine.",
"version": "0.1.0",
"author": {
"name": "Masayoshi Mizutani"
},
"license": "Apache-2.0"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[epic on Agent Plugins Marketplace](https://pluginsmp.com/plugins/epic-3)