What problem does it solve? Turning an agreed spec or ticket into working code often stalls on unclear scope, skipped design review, and missing tests. This Skill drives the implementation step end to end: it picks up the next actionable ticket when none is given, enforces a design checkpoint before coding, and routes the finished work into code review. ## Core Features & Use Cases - Automatic ticket pickup: When no spec is supplied, it claims the next ready, unassigned ticket from a Beads tracker using bv --robot-next and atomic br update --claim, avoiding double-assignment. - Design-before-code gate: Invokes the blueprint skill to present the design for approval before any non-trivial change, skipping only trivial fixes like renames. - Test-driven implementation: Applies the tdd skill at pre-agreed seams, treating a ticket's Rules & Examples map as the scenario list with one test per example. - Use Case: A developer finishes planning and says "implement the CSV export ticket." The Skill claims the ticket, shows the design for approval, writes tests per example, implements the change reusing existing code via ponytail, and hands off to code-review. ## Quick Start Use the implement skill to build the CSV export ticket from our tracker.