What problem does it solve? Building Spring Boot features without consistent structure leads to tangled controllers, missing validation, and inconsistent error handling. This Skill guides AI-assisted development of Java backend features so every change follows Controller → Service → Repository boundaries with proper DTOs, validation, and exception mapping. ## Core Features & Use Cases - Layered Feature Implementation: Enforces Controller → Service → Repository/Adapter boundaries with constructor injection, DTOs, and parameter validation. - Change-Level Routing: Uses change-router to classify work as L0 (minimal fix), L1 (lightweight design card), or L2/L3 (API/data contract first) before coding. - Quality Gates: Produces layered implementation plans, API/DTO change lists, test scope, and risk notes, then hands off to testing and review skills. - Use Case: When asked to add a new order-management REST endpoint, the Skill first classifies the change level, drafts the API contract, implements the controller, service, and repository layers with unified exception handling, then triggers the spring-boot-testing workflow. ## Quick Start Ask the AI to implement a new Spring Boot REST endpoint for creating orders, including the service layer, repository, validation, and error handling.