What problem does it solve? Building a complete CRUD feature in a Spring Boot application requires coordinating many layers — JPA entity, Flyway migration, repository, service, controller, and Thymeleaf template — while keeping naming consistent and respecting project conventions. This Skill orchestrates that entire sequence deterministically so nothing is skipped or inconsistent. ## Core Features & Use Cases - Deterministic orchestration: Invokes the track's child generator skills in order — entity plus Flyway migration, repository plus service, then controller plus Thymeleaf template — validating each stage before proceeding. - Governance enforcement: Applies the stack's Golden Rules (RO-SB1…8), including mockup approval before code (RO-06), read-record DTOs instead of exposing JPA entities to views (RO-SB4), and mandatory test execution with hex-color scanning. - Boundary routing: Recognizes when a request belongs elsewhere — a single layer, a JavaFX desktop app, a full system lifecycle, or a frontend-only task — and directs to the correct skill instead of doing the wrong work. - Use Case: Ask to "build the complete Categoria feature from database to admin screen" in an existing Spring Boot app, and it chains entity creation, migration, service layer, and an accessible Thymeleaf screen, closing with mvn test and a structured report. ## Quick Start Use the spec-springboot-crud-feature skill to create the complete CRUD feature for the Categoria entity, from database migration to the admin screen, in my existing Spring Boot project.
