Run Issue Tree

Plan and execute wave-based GitHub Issue trees with parent + sub-issue nesting, label-driven state, agent-ready issue bodies, and runtime-native worker dispatch.

When to use

Use this skill if you are:

• planning a GitHub Issue tree from a spec, PRD, or epic — splitting it into parent + sub-issues with wave labels
• creating an "epic" or "tracking issue" with nested sub-issues and Blocked-by / Blocks dependencies
• executing an existing GitHub Issue tree wave-by-wave through gh and runtime-native subagent dispatch
• given a GitHub issue URL or number and asked to "run it", "execute the tree", or "work the next wave"
• decomposing work into wave:0-foundation, wave:N, status:ready / in-progress / needs-review / failed labels
• writing agent-ready issue bodies with BSV Definition of Done, ownership protocol, and explicit blockers
• transitioning closed leaf children up to a parent closure queue and verifying parent DoD

Do not use this skill if you are: