github-mcp-orchestrator

Transform user requests into structured GitHub epics with child issues.

Updated Dec 21, 2025
One-click install
npx skills add https://github.com/cstarlea/agent-skill-orchestrator --skill github-mcp-orchestrator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-mcp-orchestrator
Source: https://github.com/cstarlea/agent-skill-orchestrator/tree/main/.claude/skills/github-mcp-orchestrator
Command: npx skills add https://github.com/cstarlea/agent-skill-orchestrator --skill github-mcp-orchestrator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates turning user feature requests, PRDs, bugs, or ideas into a clearly defined GitHub epic with structured child issues. Each child includes explicit acceptance criteria, definition of done, labels, and explicit dependencies, helping teams plan, track, and automate work without manual guesswork.

Core Features & Use Cases

  • Epic + Child Creation: Automatically creates a single epic and multiple domain-scoped child issues (frontend, backend, infra, etc.).
  • Structured Metadata: Each issue includes a Definition of Done, Acceptance Criteria, labels, estimates, and explicit dependencies.
  • Template-Driven Output: Uses standard epic/task templates to ensure consistency across repos.
  • No-Duplicate Policy: Scans for related issues to avoid duplicates and surface existing epics when appropriate.

Quick Start

Create an epic titled "Spotify Playlist Integration" with four child tasks for backend API, frontend UI, integration tests, and documentation, all linked to the epic with clear dependencies and criteria.

Frequently Asked Questions about github-mcp-orchestrator

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

FAQPage Schema
How do I turn a feature request into structured GitHub issues automatically?

Transform feature requests, PRDs, or ideas into a GitHub epic with multiple child issues by parsing the request, generating structured tasks with acceptance criteria, dependencies, labels, and estimates, then creating them via GitHub MCP tools to produce an issue map with direct links.

Can I automatically detect duplicate issues when creating GitHub epics?

Yes, the Skill scans for related existing issues and labels before creating new ones, surfacing duplicate epics and preventing redundant work while applying your repository's labeling taxonomy consistently.

How do I break down a rough idea into domain-scoped child tasks on GitHub?

Provide your request and the Skill decomposes it into frontend, backend, infrastructure, and documentation tasks, each with explicit acceptance criteria, definition of done, and dependency relationships linked to the parent epic.

What should I include in my request for the best GitHub issue output?

Include feature descriptions, requirements, or bug details—the Skill extracts functional scope, generates structured metadata like acceptance criteria and estimates, then creates a complete epic with child issues and dependency chains.

Does task decomposition work for bug reports and documentation tasks?

Yes, the Skill handles feature requests, PRDs, bug reports, and rough ideas equally, decomposing each into domain-scoped child tasks with acceptance criteria, labels, and dependencies appropriate to the work type.

Can I customize issue templates and dependency relationships in the output?

The Skill uses standard epic and task templates to ensure consistency, establishing explicit dependency relationships and applying repository labeling taxonomy so all issues conform to your team's workflow standards.