multi-agent-issue-management

Coordinates task assignment and issue tracking across multiple AI coding agents to prevent git conflicts.

Updated Jul 26, 2026
One-click install
npx skills add https://github.com/Dhruv-Ghanchi/Portfolio-Webiste --skill multi-agent-issue-management-dhruv-ghanchi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: multi-agent-issue-management
Source: https://github.com/Dhruv-Ghanchi/Portfolio-Webiste/tree/main/.agent/skills/multi-agent-issue-management
Command: npx skills add https://github.com/Dhruv-Ghanchi/Portfolio-Webiste --skill multi-agent-issue-management-dhruv-ghanchi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When multiple autonomous AI agents (Google Jules, Cloud Codex, Antigravity) work in the same codebase, they can overwrite each other's changes and create git conflicts. This Skill provides a structured workflow for assigning isolated tasks, tracking issues with unique IDs, and coordinating handoffs between agents. ## Core Features & Use Cases - Agent Role Allocation: Assigns work based on directory isolation, feature isolation, or sequential dependence so no two agents edit the same file in parallel. - Unique Issue Tracking: Creates issues with sequential IDs (e.g., ISSUE-001) stored as Markdown files in the issues/ directory using a standardized template. - Conflict Zone Declaration: Each issue explicitly lists allowed files and forbidden conflict zones, plus branch naming and PR strategy. - Use Case: You want Codex to build a backend API while Jules builds the frontend UI. Create two issues with non-overlapping file scopes, assign each to the right agent, and track completion status without merge collisions. ## Quick Start Create a new issue for Codex to implement the backend endpoint and assign the UI work to Jules with separate file scopes.

Frequently Asked Questions about multi-agent-issue-management

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

FAQPage Schema
How do I prevent git conflicts when multiple AI agents work on the same repo?

Assign each agent an isolated scope using directory isolation, feature isolation, or sequential dependence. Document allowed files and conflict zones in a tracked issue so no two agents edit the same file in parallel.

How do I create a tracked issue for an AI coding agent?

Use the issue template to define a unique sequential ID like ISSUE-001, assign a primary agent, list allowed directories and conflict zones, and save it as ISSUE-[ID]-[slug].md in the issues directory.

What is the issue ID naming convention for multi-agent tasks?

Each issue uses a 3-digit zero-padded sequential ID in the format ISSUE-001, stored as a Markdown file named ISSUE-[ID]-[slug].md inside the skill's issues directory.

Can two agents work on the same file at the same time?

No. The workflow rules state two agents should never be assigned to edit the same file in parallel. If one agent needs changes in another's file, it must update the issue and wait for handoff.

When should I create a master coordination plan instead of single issues?

Create a master plan for complex features spanning multiple agents, mapping the sequence of work such as backend schema first, then configuration, then UI, with explicit file lists for each step.