What problem does it solve? Turning a spec or a set of tickets into committed, tested code requires disciplined sequencing: knowing which ticket is unblocked, keeping acceptance criteria in view, and reporting progress without drowning observers in noise. This Skill drives that loop so implementation stays honest and traceable. ## Core Features & Use Cases - Frontier-based ticket execution: Works only tickets whose blockers are all closed, re-reading acceptance criteria before starting each one. - Paired progress reporting: Reports ticket start and close as matched pairs via the cockpit script, so a stalled session is visible instead of silent. - TDD and verification: Applies test-driven development at the seams the spec agreed on, typechecks and runs relevant tests as it goes, and runs the full project check at the end. - Use Case: After running /feature to produce a spec and tickets, invoke this Skill to implement each unblocked ticket in order, commit per ticket, run the full check, and hand off to /code-review. ## Quick Start Ask the AI to implement the work described in the current spec or the open tickets on the issue tracker, working the unblocked frontier one ticket at a time.
