multi-issue-flow

Automate issue-driven development from GitHub Issues to PR creation via MCP.

2|Updated Apr 6, 2017
One-click install
npx skills add https://github.com/shiiman/dotfiles --skill multi-issue-flow
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-issue-flow
Source: https://github.com/shiiman/dotfiles/tree/main/ai/codex/skills/multi-issue-flow
Command: npx skills add https://github.com/shiiman/dotfiles --skill multi-issue-flow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end issue-driven development workflows starting from a GitHub Issue, coordinating a multi-agent MCP flow to assign roles, initialize workspaces, spawn workers, and deliver a PR without manual handoffs.

Core Features & Use Cases

  • End-to-end MCP orchestration: create owner/admin/workers, initialize a workspace, dispatch tasks, monitor progress, and finalize a PR.
  • Issue-driven execution: starts from a tracked GitHub Issue and uses the issue number as a session identifier for all MCP activities.
  • Parallel worker coordination: enables concurrent workstreams with status feedback and automatic aggregation into a PR.

Quick Start

Initiate the multi-issue-flow from a GitHub Issue to orchestrate the MCP roles, branch creation, worker execution, and PR generation.

Frequently Asked Questions about multi-issue-flow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate GitHub issue-driven development with parallel execution?

Automate GitHub issue-driven development by using a multi-agent MCP to spawn owner, admin, and worker roles. The flow initializes a workspace, dispatches parallel tasks, monitors progress, and automatically aggregates outputs into a pull request.

What is multi-agent MCP orchestration for GitHub issues?

Multi-agent MCP orchestration coordinates concurrent workstreams starting from a tracked GitHub Issue. It assigns roles, manages branch creation, spawns workers for parallel execution, and delivers a final PR without manual handoffs.

Can I use parallel workers to open PRs from a single GitHub Issue?

Yes, parallel worker coordination enables concurrent workstreams with status feedback. Workers execute tasks dispatched from a single GitHub Issue, and their outputs are automatically aggregated into a unified pull request.

How do I start an end-to-end issue-driven PR workflow?

Initiate the workflow directly from a tracked GitHub Issue. The issue number acts as a session identifier for all MCP activities, triggering role creation, workspace initialization, task dispatch, status polling, and PR creation.

Does this issue-driven workflow require manual handoffs between agents?

No manual handoffs are required. The end-to-end MCP orchestration automatically manages role creation, task dispatch, worker status polling, and branch aggregation to finalize the pull request seamlessly.