workflow
v0.13.0Issue-driven and parallel automation: next-issue, orchestrate, golem, file-issue, provision-agent, and the bundled scripts they call.
By Josh Hall1 GitHub starsUpdated 2 weeks ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 10 skill or MCP entries
- Source updated
- Sep 9, 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 workflow for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install workflow-2@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/joshjhall/librarianClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugins/workflow/.
Plugin files
├── .claude-plugin/plugin.json├── skills/file-issue/SKILL.md├── skills/golem/SKILL.md├── skills/next-issue/SKILL.md├── skills/orchestrate/SKILL.md├── skills/provision-agent/SKILL.md├── skills/rebase-generated/SKILL.md├── skills/rebase-imports/SKILL.md├── skills/rebase-lockfile/SKILL.md├── skills/rebase-version/SKILL.md└── skills/ship-issue/SKILL.md
Included Skills10
Structured GitHub/GitLab issue creation with auto-labeling and scope enforcement. Use when filing new issues, enriching existing issues, or preparing issues for agentic workflows like /workflow:next-issue.
Run a single issue end-to-end as a solo "golem" in the current session — create an isolated git worktree, work the issue there through the next-issue → ship-issue pipeline at a chosen autonomy level (L1–L4), then tear the worktree down. Use when you want one issue worked with full golem rigor (including the adversarial pre-PR review — the Workflow tool with ship-issue/workflow.js) and worktree isolation, without an orchestrator, tmux, or containers. For 2+ parallel issues, use /workflow:orchestrate instead.
Issue-driven development workflow that picks the next issue by severity/effort priority and creates an implementation plan. Use when working through a backlog, picking up the next issue, or resuming in-progress work. After implementation, use /workflow:ship-issue to deliver.
Master orchestrator for PR-per-golem parallel work. Dispatch golems (one issue/branch/worktree/PR each) running the next-issue → ship-issue pipeline at a chosen autonomy level (L1–L4), monitor PR + issue-label state, surface progress, rebase across PRs, and run an integration train that lands a batch of green PRs (merge→rebase→merge) with one approval. Use when running 2+ independent issues in parallel, watching golem PRs, or integrating agent work. Local-merge topology preserved as opt-in.
Provision headless agent containers from devcontainer config. Generates docker-compose, creates worktrees, starts containers with tmux-attached Claude Code sessions. Use when spinning up container agents for parallel work.
Resolve merge conflicts in generated files by re-running the generator. Use when conflicts occur in protobuf outputs, code-generated files, or auto-generated migrations.
Resolve import ordering merge conflicts by combining, deduplicating, and sorting. Use when both sides of a merge added imports to the same block.
Resolve lock file merge conflicts by regenerating from the manifest. Use when merge conflicts occur in package-lock.json, Cargo.lock, go.sum, or similar lock files.
Resolve version number merge conflicts by taking the higher version. Use when both sides of a merge bumped version numbers independently.
Ship the current next-issue work — commit, deliver (PR or push), label the issue, and optionally loop back. Use after implementation and testing are complete for an issue started with /workflow:next-issue.
Plugin manifests1
{
"name": "workflow",
"version": "0.13.0",
"description": "Issue-driven and parallel automation: next-issue, orchestrate, golem, file-issue, provision-agent, and the bundled scripts they call.",
"author": {
"name": "Josh Hall",
"url": "https://github.com/joshjhall"
}
}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.
[workflow on Agent Plugins Marketplace](https://pluginsmp.com/plugins/workflow-2)