What problem does it solve? When a ticket's direction is clear and its blast radius is small, running the full gated architect → developer → code-review → QA pipeline adds unnecessary overhead. This Skill provides a short path that implements afk-labeled work in a single session while still enforcing pre-flight checks, TDD, and explicit developer approval before committing. ## Core Features & Use Cases - Ticket resolution and claiming: Accepts a named ticket, or auto-picks the next open, unblocked, unclaimed afk ticket from an epic on GitHub, GitLab, or a local .scratch tracker, and claims it to prevent parallel-session conflicts. - Pre-flight gating: Fails fast on hitl tickets (routing them to /to-guide), checks and clears blockers, marks work in progress, and enforces branch rules against the ticket's declared integration branch. - Controlled coding loop: Applies TDD, runs typechecking and tests, optionally invokes /code-review with explicit developer consent, and commits and pushes only after explicit permission. - Use Case: A developer names issue #42, an afk ticket with a clear spec. The Skill verifies it is unblocked, creates the correct feature branch from the integration branch, implements the change with tests, asks before reviewing and committing, then suggests /to-pull-requests as the next step. ## Quick Start Ask the agent to fast-implement ticket number 42 and confirm each approval prompt as it appears.
