What problem does it solve? Coordinating multi-session development work on GitHub — picking up issues, dispatching subagents, reviewing PRs, and keeping a project board honest — breaks down when state lives in chat memory instead of on GitHub. This Skill enforces a disciplined, board-driven workflow where every session can be reconstructed from GitHub state alone. ## Core Features & Use Cases - Issue-driven execution: Resolves a target (issue, epic, milestone, triage queue, or next-ready), claims it, gates on planning readiness, and drives it through implementation, contextless review, merge, and live validation. - Solo and orchestrated modes: Works alone on single issues or acts as the sole orchestrator of parallel implementer, fix-round, reviewer, and validation subagents with strict role separation. - State on GitHub, not in chat: Claims, board columns, epic event comments, session logs, and structured handoffs keep milestones, epics, and issues as the single source of truth across sessions and crashes. - Use Case: Tell the agent "work epic 1176 in parallel overnight" — it claims the epic, dispatches implementers per issue, routes every PR through a fresh reviewer, files deferred findings, runs maintenance passes, and delivers a morning brief with metrics. ## Quick Start Ask the agent to work a specific issue, epic, or milestone — for example, "work issue 1140 solo" or "work the triage queue" — and it will orient from the board, claim the work, and execute the full workflow.
