What problem does it solve? Unattended sprint development requires deciding, on every scheduled run, which of many possible tasks (PR review follow-up, spec sync, backlog grooming, new sprint kickoff, hygiene audits) should execute first. This Skill provides a single decision-tree router that evaluates repository state via GitHub Issues, PRs, and labels, then executes exactly one branch per run so a cron routine can advance development autonomously. ## Core Features & Use Cases - Decision-tree routing: Evaluates 10 prioritized branches per firing (breaking-change response, own-PR collection, in-progress sprint resume, SP-to-Issue sync, new sprint kickoff with TDD, improvement issue digestion, retro-try handling, hygiene, weekly refinement, spec-sync verification) and runs only the first matching one. - API channel detection: Re-determines every run whether to use GitHub MCP tools, the gh CLI, or curl REST fallback, with fail-closed no-op behavior when all channels are unavailable. - Production drift inspection: Detects when main HEAD diverges from the deployed Cloudflare Workers build, re-triggers builds, and escalates via Slack with threshold-based notification suppression. - Use Case: Configure a 2-hour cron routine; each firing the router checks for open PRs needing review, stale in-progress issues, or a ready SP-n issue, then either resumes interrupted work or starts the next sprint without human intervention. ## Quick Start Ask the AI to run the sprint self-driving routine by saying "run the sprint cycle router and advance development for this repository".
