java-spring-workflow

To implement a Spring controller with request response contracts, use an approved plan as the source of truth and apply repository rules for Request/Response naming and service naming conventions during coding to prevent contract drift.

A self-review loop for Java Spring code style compliance is a targeted checklist review focused on service naming, request/response conventions, time-handling rules, package structure, and dependencies, followed by fixing violations before verification.

Yes, you can use this workflow to revise existing Spring services and use cases by applying repository Java code style rules, running the self-review loop on the diff, and verifying targeted diagnostics and build checks.

To handle deterministic time in Spring implementation, apply repository time-handling rules during the coding phase and verify compliance through the self-review checklist before running targeted tests or build checks.

Yes, you need an approved plan before starting Java Spring implementation because the workflow prioritizes the approved plan as the source of truth and applies Spring contract and structure rules during coding based on it.

The best way to verify Spring code changes is to run the smallest relevant diagnostics, tests, and build checks recommended by the workflow, avoiding completion claims without evidence from targeted verification results.