What problem does it solve? Turning a written spec or ticket into finished, verified code requires coordinating dependency checks, test-driven development, typechecking, and status tracking — steps that are easy to skip or do out of order. This Skill enforces that disciplined implementation workflow so work lands correctly and downstream stories unblock properly. ## Core Features & Use Cases - Dependency-aware start: Reads the story's Blocked by cell in the tracker before starting, distinguishing true blockers from shared primitives that must be built inline. - Structured implementation loop: Applies test-driven development at pre-agreed seams, runs typechecking and single test files regularly, and executes the full test suite once at the end. - Tracker lifecycle management: Flips the story status to Done, runs dependency sync to clear other rows' blockers, and updates the provided-capabilities section when outputs change. - Use Case: A developer picks up an epic story from the tracker, confirms its dependencies are cleared, implements it with TDD, reviews the result, and marks it Done so dependent stories become startable. ## Quick Start Ask the assistant to implement the work described in a specific spec or ticket ID from the tracker.