gen-code

Generating a Spring Boot microservice from JIRA stories requires modernization artifacts like functional specs, technical specs, and analysis files. This Skill translates those inputs into a complete, buildable Spring Boot 4.x project with entities, controllers, and a traceability manifest.

Scaffolding a Spring Boot 4.x project requires modernization artifacts including analysis.md, fingerprint.json, funcspec.md, techspec.md, jira-stories.md, and contracts.json. These files must be located in the modernization-output directory to produce idiomatic code with database migrations.

Spring Boot microservice generation enforces Java 17+ and Jakarta EE 9+ runtime requirements. The generated project includes idiomatic Spring Boot 4.x conventions, OpenAPI docs, Flyway or Liquibase database migrations, and test containers-based integration tests.

Spring Boot microservice generation includes database migrations using Flyway or Liquibase and test containers-based integration tests. The output provides a production-ready project with a code-manifest.json mapping that preserves traceability back to original modernization sources.

Translating legacy business logic into idiomatic Spring Boot conventions is achieved by processing modernization artifacts through automated code generation. This approach preserves critical behaviors and data models while producing clean, maintainable Spring Boot 4.x microservices with traceability manifests.

Modernization artifacts provide structured intent from analysis and JIRA stories that automated code generation translates into consistent Spring Boot projects. This ensures traceability back to original sources while producing entities, repositories, services, and messaging integration without manual scaffolding errors.