run-agents

Delegate GitHub issue spec steps to dedicated subagents with per-step commits.

Updated Mar 14, 2026

Search Tags:#automation #workflow #github #verification #subagent #issue #orchestrate

Ready to run

npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill run-agents

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: run-agents
Source: https://github.com/ryan-mahoney/ryan-llm-skills/tree/main/skills/run-agents
Command: npx skills add https://github.com/ryan-mahoney/ryan-llm-skills --skill run-agents

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinate end-to-end implementation by delegating each spec step to a dedicated subagent.

Core Features & Use Cases

Orchestrates end-to-end execution of GitHub issue specs by delegating each step to specialized subagents.
Enforces surgical, low-risk changes with per-step verification and per-step commits to maintain a clean history.
Supports staged, auditable workflows and per-step quality checks to ensure alignment with the original spec.

Quick Start

Parse the issue spec with gh issue view <issue-number> and delegate the first step to a dedicated subagent.

Frequently Asked Questions about run-agents

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

FAQPage Schema

How do I orchestrate GitHub issue implementation using subagents?▼

To orchestrate GitHub issue implementation, this Skill delegates each spec step to a dedicated subagent. It coordinates end-to-end execution by parsing the issue and assigning isolated tasks to specialized agents for staged changes.

What is the best way to ensure isolated commits for each step of a GitHub issue spec?▼

Isolated commits for each step are enforced by delegating spec tasks to dedicated subagents. This approach guarantees surgical, low-risk changes by verifying and committing each step independently to maintain a clean history.

How does subagent orchestration maintain auditable workflows for staged changes?▼

Subagent orchestration maintains auditable workflows by enforcing per-step isolation and per-step verification. Each dedicated subagent produces surgical changes with quality checks, ensuring full traceability and alignment with the original issue spec.

Can I use this automation workflow for staged changes without external dependencies?▼

Yes, you can use this workflow without external dependencies. It requires only GitHub issue specifications and coordinates stepwise, isolated execution internally to produce auditable changes via per-step commits.

When do I need to delegate issue implementation to dedicated subagents?▼

You need to delegate issue implementation to dedicated subagents when GitHub issue specifications require staged, auditable changes. This ensures per-step isolation, surgical modifications, and verified commits for traceability and safety.

Why does per-step verification matter for orchestrating issue specs?▼

Per-step verification matters because it enforces surgical, low-risk changes during issue orchestration. By verifying each dedicated subagent's output independently, you ensure alignment with the original spec and maintain a clean commit history.