What problem does it solve? Coordinating the implementation of multiple already-specced GitHub issues manually is error-prone: issues get done out of order, scope creep derails the branch, and discovered blockers stall the whole batch. This Skill runs a given ordered list of issue numbers one at a time in fresh subagents, all landing on a single shared branch and PR. ## Core Features & Use Cases - Ordered batch implementation: Executes a user-supplied sequence of issue numbers (e.g. 281, 280, 282) strictly in the given order, one issue at a time. - Fresh subagent per issue: Each issue is implemented in an isolated subagent context, keeping work scoped and reviewable. - Autonomous scope-creep triage: Small growth is auto-expanded into the current work, while large growth or discovered blockers are spun off and re-queued as new issues. - Use Case: A maintainer wants issues 281, 280, and 282 shipped as one PR. They invoke the sequence, and each issue is implemented in order on the shared branch, with any oversized discoveries automatically filed as follow-up issues. ## Quick Start Ask the agent to implement issues 281, 280, and 282 in that order as a single PR using the issue-sequence workflow.
