What problem does it solve? Writing a new entity in a CQRS-style Spring WebFlux backend means hand-creating a dozen coordinated files — migration SQL, entity, repository or mapper, commands, queries, views, validators, exceptions, and web routes — each following strict project conventions. This Skill generates that entire scaffold deterministically from templates, in either manual mode or driven by a plan.json spec. ## Core Features & Use Cases - Dual persistence profiles: Generates R2DBC (reactive repository, UUID converters) or MyBatis (mapper interface, XML, type handlers) variants, plus functional or annotated web layers. - Spec-driven and manual modes: Reads entities, commands, queries, endpoints, and validation rules from plan.json, or accepts inline field definitions with flags like unique, max=N, and pattern=email. - Pipeline-safe bookkeeping: Uses progress files, demotion checks, and a lock file so regenerated scaffolds never silently destroy downstream pipeline state. - Use Case: Run be-crud Employee email:String:unique:pattern=email displayName:String:max=20 to produce a migration, entity, repository, command executor, query processors, router/handler, validator, and exceptions for the hr domain in one pass. ## Quick Start Ask the assistant to scaffold a new Employee entity with a unique email field and a display name limited to 20 characters using the be-crud skill.