Menu
Run a GitHub issue end-to-end in this repository using the committed isolated-worktree workflow. Use when the user invokes $gh-task, asks to run a GitHub task, or provides a GitHub issue number,
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Tree-aware multi-agent GitHub-issue pool. Conductor manages task-tree from task-splitting-evaluation, executing depth-first per branch while parallelizing roots/orphans. Each worker agent owns its subtree lifecycle. Conductor tracks state (pending/started/in-progress/completed/halted) in GitHub + .claude/task-state.json, passes context from parent issue comments, auto-halts dependents. Use after task-splitting-evaluation to execute the resulting task tree.
Recursive pre-implementation GitHub task splitting and evaluation flow. Use when the user wants Claude agents to evaluate unhandled tasks, skip already-processed tasks, mark easy leaves with detailed executor-ready comments, split broad tasks into GitHub subtasks, and keep recursing until every leaf is well described with a selected LLM/model.
Based on SOC occupation classification
| name | gh-task |
| description | Run a GitHub issue end-to-end in this repository using the committed isolated-worktree workflow. Use when the user invokes $gh-task, asks to run a GitHub task, or provides a GitHub issue number, |
Run one GitHub issue through the repository workflow in docs/commands/gh-task.md.
Treat that file as the canonical procedure and load it before doing task work.
Accept a GitHub issue URL, #123, or 123.
Resolve the numeric issue id and use that exact id as the worktree and branch name.
1.Follow docs/commands/gh-task.md exactly unless the current user gives a newer conflicting instruction.
2.Keep all implementation work inside .worktrees/<issue-id> after the worktree is created.
