gh-project-implement

Automate concurrent implementation of GitHub Project issues by priority with DAG-based scheduling.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/wscffaa/claude-gh-skills --skill gh-project-implement
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-project-implement
Source: https://github.com/wscffaa/claude-gh-skills/tree/main/gh-project-implement
Command: npx skills add https://github.com/wscffaa/claude-gh-skills --skill gh-project-implement

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, git, codeagent-wrapper, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the end-to-end execution workflow for GitHub Project issues by applying priority-based concurrency, enabling teams to move sprint work forward without manual coordination.

Core Features & Use Cases

  • Priority-driven parallel execution: Processes P0 → P1 → P2 → P3 batches with dynamic concurrency, maximizing throughput while respecting dependencies.
  • Dependency-aware scheduling: Uses a DAG-like model to ensure an issue only starts after its dependencies are completed, with graceful fallbacks if cycles exist.
  • Worktree isolation and automation: Creates a separate Git worktree per issue, runs code development tasks via a codeagent wrapper, then reviews and merges PRs automatically where possible.
  • Progress tracking and cleanup: Provides real-time progress reports and a cleanup routine to remove stale resources and branches after completion.

Quick Start

Trigger the skill against a target project by number, for example: gh-project-implement 1

Frequently Asked Questions about gh-project-implement

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

FAQPage Schema
How do I automate concurrent implementation of multiple GitHub Project issues?

Automate concurrent implementation of GitHub Project issues by processing priority batches (P0-P3) with dynamic concurrency. The tool uses DAG-based scheduling to respect dependencies and creates isolated Git worktrees for each issue to parallelize sprint execution safely.

How does dependency-aware scheduling work for parallel sprint execution?

Dependency-aware scheduling uses a DAG-like model to ensure an issue only starts after its dependencies are completed. This prevents blocking during parallel sprint execution and includes graceful fallbacks if dependency cycles exist within the GitHub Project workflow.

Do I need Git worktrees to manage concurrent GitHub issue development?

Git worktrees are automatically created per issue to isolate concurrent development tasks. This isolation prevents branch conflicts while the automation runs code tasks, reviews, and merges PRs for multiple GitHub Project issues simultaneously.

What's the best way to handle automated PR creation and merging for sprint backlogs?

Automated PR creation and merging for sprint backlogs is handled by running code development tasks via a codeagent wrapper within isolated worktrees. The system reviews and merges PRs automatically where possible after completing priority-driven parallel execution.

Can I use priority-based batch processing for GitHub Project maintenance across teams?

Priority-based batch processing supports GitHub Project maintenance and cross-team workflows by processing P0 through P3 batches. It maximizes throughput with dynamic concurrency while managing interdependencies for rapid progress across multiple team backlogs.

How do I clean up stale branches and worktrees after automated issue processing?

Cleanup of stale branches and worktrees after automated issue processing is handled by a built-in routine that removes leftover resources. This runs alongside real-time progress reports to ensure repository hygiene once parallel sprint execution completes.