issue-pipeline

Orchestrates GitHub issue lifecycle with parallel, worktree-isolated sub-agents across plan, implement, review, merge phases.

58|6|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/fagemx/gstack-game --skill issue-pipeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: issue-pipeline
Source: https://github.com/fagemx/gstack-game/tree/main/.claude/skills/issue-pipeline
Command: npx skills add https://github.com/fagemx/gstack-game --skill issue-pipeline

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Orchestrates the full lifecycle of GitHub issues through parallel sub-agents to accelerate delivery and governance.

## Core Features & Use Cases

  • End-to-end issue lifecycle management with plan, implement, review, and merge phases
  • Parallel, worktree-isolated execution per issue to prevent cross-contamination
  • Automatic status reporting and PR creation to streamline collaboration

### Quick Start Execute an end-to-end issue pipeline across plan, implement, and review phases using parallel worktree-isolated agents.

Frequently Asked Questions about issue-pipeline

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

FAQPage Schema
How do I automate the end-to-end GitHub issue lifecycle from planning to merging?

Automate the GitHub issue lifecycle by orchestrating plan, implement, review, and merge phases using parallel sub-agents. This approach manages multi-issue batches end-to-end while providing status dashboards, automatic PR creation, and merge controls.

Can I run parallel issue implementations in Git worktrees without cross-contamination?

Run parallel issue implementations in isolated Git worktrees to prevent cross-contamination. Worktree-isolated sub-agents execute per issue independently, allowing multiple branches to progress simultaneously without interfering with each other's file changes.

How do I skip specific phases like review or merge for certain GitHub issues?

Skip specific phases for certain GitHub issues using per-issue flags during pipeline orchestration. You can configure the end-to-end execution rules to bypass plan, implement, review, or merge stages individually for each issue in the batch.

What is the best way to orchestrate multi-issue batches in GitHub projects?

Orchestrate multi-issue batches in GitHub projects by deploying parallel sub-agents across plan, implement, and review phases. This method provides phase coordination, worktree isolation, real-time status dashboards, and streamlined PR creation for batch delivery.

Does parallel pipeline orchestration work for GitHub issues requiring code review and PR creation?

Parallel pipeline orchestration works for GitHub issues requiring code review and PR creation by coordinating these phases automatically. Sub-agents handle implementation in isolated worktrees and generate pull requests, allowing the review and merge phases to proceed systematically.

How do I track the status of parallel GitHub issue pipelines?

Track the status of parallel GitHub issue pipelines using built-in status dashboards. These dashboards monitor phase coordination across plan, implement, review, and merge stages, providing visibility into the progress of worktree-isolated sub-agents.