Subissue Orchestration

A command-line tool for managing and automating feed-forward neural networks.

5|3|Updated Nov 30, 2025
One-click install
npx skills add https://github.com/constellos/claude-code-plugins --skill subissue-orchestration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Subissue Orchestration
Source: https://github.com/constellos/claude-code-plugins/tree/main/plugins/github-orchestration/skills/subissue-orchestration
Command: npx skills add https://github.com/constellos/claude-code-plugins --skill subissue-orchestration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Subissue Orchestration tackles the complexity of managing large epics by automatically creating and linking subissues under a parent issue. It leverages GitHub's native sub-issues API (GA 2025) for accurate parent-child relationships that surface in the GitHub UI and Projects, with a markdown checklist fallback for compatibility.

Core Features & Use Cases

  • Native Sub-Issues API: create and link subissues to a parent epic, visible in the UI and Projects, supporting up to 100 subissues per parent and 8 levels of nesting, with cross-repository support.
  • Subissue Creation: use the sync-task-to-subissue workflow to automatically link created subissues via the native API.
  • Checklist Fallback: when native sub-issues are unavailable, maintain a checklist in the parent issue and keep it synchronized.
  • Bulk Creation & PR Coordination: spawn multiple subissues from a list and coordinate with stacked PRs so merging closes the appropriate subissues.
  • Auto-Sync & Lifecycle: keep parent and subissues in sync as work progresses, including status updates and re-linking when needed.

Quick Start

Create a parent epic and then generate subissues linked to it.

PARENT=$(gh issue create --title "Authentication System" --label "epic" --body "## Subtasks\n\n- [ ] OAuth\n- [ ] Email auth\n- [ ] Password reset" --json number -q .number)

gh issue create --title "OAuth integration" --label "task" --body "Parent Issue: #$PARENT" gh api repos/{owner}/{repo}/issues/$PARENT/sub_issues -X POST -f sub_issue_id=$SUBISSUE_ID

Frequently Asked Questions about Subissue Orchestration

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

FAQPage Schema
How do I break down GitHub epics into subissues automatically?

Break down GitHub epics by automatically creating and linking subissues under a parent issue using the native GitHub sub-issues API. This provides accurate parent-child relationships that surface directly in the GitHub UI and Projects.

What is the best way to coordinate stacked PRs with subissues?

Coordinate stacked PRs by spawning subissues from a list and linking them to your pull requests, ensuring that merging a stacked PR automatically closes the corresponding subissue and updates the parent epic.

Does GitHub sub-issues API support cross-repository linking?

Yes, GitHub native sub-issues support cross-repository linking, allowing you to create and link subissues across different repositories with up to 8 levels of nesting and 100 subissues per parent.

What happens to parent issue checklists when native sub-issues are unavailable?

When native sub-issues are unavailable, a markdown checklist is maintained in the parent issue and kept synchronized. This fallback ensures continuous progress tracking within your existing GitHub environment.

How do I sync task status between parent epics and subissues?

Sync task status by enabling auto-synchronization between parent epics and subissues as work progresses. This automatically applies status updates and re-links subissues when needed to maintain accurate project tracking.