skills.rest
drdatarulz
drdatarulzCOMMUNITY
Explore all skills by this author →
GitHub

orchestrate

Spawn per-ticket subagents to implement GitHub project tickets sequentially.

3|Updated Feb 20, 2026
Search Tags:#automation#workflow#github#subagent#ticket#project-management#orchestrate
One-click install
npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill orchestrate-drdatarulz
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: orchestrate
Source: https://github.com/drdatarulz/TI-Engineering-Standards/tree/main/skills/archive/orchestrate-v1
Command: npx skills add https://github.com/drdatarulz/TI-Engineering-Standards --skill orchestrate-drdatarulz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Sequentially implement multiple GitHub Project tickets by spawning a fresh subagent per ticket. It manages pre-flight checks, board updates, merging, and a final session summary to keep work organized and auditable.

Core Features & Use Cases

  • Spawn a dedicated subagent for each ticket to isolate implementation work.
  • Perform pre-flight checks: read the ticket, update main, verify or set git hooks, create a branch, and move the ticket to In Progress on the project board.
  • Coordinate progress, merging, and post-work summarization, including closing or archiving tasks as appropriate.

Quick Start

Provide the mode and a comma-separated list of ticket identifiers to initiate the orchestrator and begin processing them in sequence.

Frequently Asked Questions about orchestrate

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

FAQPage Schema
How do I automate GitHub project ticket workflows with subagents?▼

GitHub project ticket workflows can be automated by spawning a dedicated subagent per ticket to sequentially execute implementation work, manage pre-flight checks, update boards, and handle merging. This isolates work and keeps multi-ticket sessions auditable.

What is the best way to track progress across multiple GitHub Project tickets?▼

Tracking progress across multiple GitHub Project tickets is handled by moving tickets to In Progress on the board, coordinating per-ticket subagent execution, and generating a final session summary to close or archive tasks as appropriate.

How do I start processing a list of GitHub tickets in sequence?▼

To start processing GitHub tickets in sequence, provide the mode and a comma-separated list of ticket identifiers to initiate the orchestrator, which then begins spawning subagents and executing the listed work sequentially.

What pre-flight checks are needed before implementing a GitHub project ticket?▼

Pre-flight checks for GitHub project ticket implementation include reading the ticket, updating the main branch, verifying or setting git hooks, creating a dedicated branch, and moving the ticket to In Progress on the project board.

Can I isolate implementation work for each GitHub ticket separately?▼

Yes, implementation work can be isolated for each GitHub ticket by spawning a fresh subagent per ticket, which ensures that pre-flight checks, execution, and merging are managed independently for organized and auditable results.

Related Skills

Explore More Software Engineering Skills→
learnzdevelopmenthublearnzdevelopmenthub
1

project-init

Initialize GitHub repositories into the Paadhai pipeline with .paadhai.json configuration.

Community
Advanced
ramonclaudioramonclaudio
4

end

Archive Claude session state and health checks to the .handoff directory.

Community
Advanced
EthansuttorEthansuttor

agent-project-board-sync

Synchronize AI swarm tasks with GitHub Projects using configurable mappings and CLI-driven workflows.

Community
Advanced
rstacruzrstacruz
13

ralph-loop

Coordinate ticket-by-ticket feature execution with isolated agent sessions and single-ticket commits.

Community
Advanced