worker-implement

Implement a vertical slice with test-driven development by planning backwards from the production code path and writing tests that import actual production code before implementation begins. This ensures full-stack ownership without dual-code paths.

Backward planning for feature implementation starts from the final production wiring path and traces dependencies backwards to define types and services. It enforces test-first verification and strict validation contracts before writing implementation code.

Vertical slice ownership is needed for Go feature development requiring full-stack ownership from types to wiring. It prevents fragmented implementation and technical debt by ensuring every slice is fully tested and wired into the production path.

The best way to enforce validation contracts during TDD implementation is integrating concrete validation cases into the definition of done for every request. This requires test-first verification of the feature's contract before service implementation.

The worker-implement skill supports safe shared-worktree git discipline by enforcing strict adherence to production-grade wiring and test-first verification. This ensures dependency injection and full-stack implementation align with validation contracts.