---
title: "aiup-spring-boot"
description: "AI Unified Process Spring Boot layers: service and REST API implementation and tests"
canonical: https://agentpluginsdirectory.com/plugins/aiup-spring-boot
last-updated: 2026-10-24
---

# aiup-spring-boot
AI Unified Process Spring Boot layers: service and REST API implementation and tests
- Slug: aiup-spring-boot
- Publisher: Simon Martinelli
- Repository: https://github.com/AI-Unified-Process/marketplace
- Manifest: aiup-spring-boot/plugin.json
- Version: 3.0.1
- Category (editorial): other
- Skills: 4 (spring-rest-test, spring-rest, spring-service-test, spring-service)
- MCP servers: 1 (JavaDocs)
- Stars: 150
- Repository created: 2026-02-28
- Repository last pushed: 2026-10-24
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/aiup-spring-boot
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What aiup-spring-boot does, in the publisher's words

aiup-spring-boot is the AI Unified Process layer plugin for the service and API layers of a Spring Boot application: the business logic with its transactions and business rules, and a REST API with RFC 9457 Problem Details, each with its test skill.

It is one layer of a stack, not a stack. Combine it with aiup-core (3.0.0 or later) and one plugin per other layer of your project. /stack records which plugin builds which layer in docs/architecture/stack.md; /use-case-implement, /use-case-test, and /use-case-coverage run the layer skills from there.

Each skill is normally run by /use-case-implement UC-XXX or /use-case-test UC-XXX, which pass the Handover of the layer below, the repository methods, the service methods and exceptions, the endpoints, to the next. Each can also be run directly, for example /spring-rest UC-001 to change only the API of a use case.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/AI-Unified-Process/marketplace/HEAD/aiup-spring-boot/README.md

## Skills

- spring-rest-test: Writes the REST API tests of a use case (UC-XXX) in a Spring Boot application: status codes, Location headers, the JSON contract (field names, date formats), RFC 9457 Problem Details bodies, and, as the integration layer of a REST service or behind an Angular client, every business rule's allowed a…
- spring-rest: Implements the REST API layer of a use case (UC-XXX) in a Spring Boot application: @RestController endpoints on top of the service layer, request and response DTO records, @Valid input validation, error mapping to RFC 9457 Problem Details with a @RestControllerAdvice, a status code per alternative…
- spring-service-test: Writes the service layer tests of a use case (UC-XXX) in a Spring Boot application: every business rule with its allowed and its rejected case, every alternative flow the service decides, and the main success scenario, called on the @Service directly. Uses @SpringBootTest with the real persistence…
- spring-service: Implements the service layer of a use case (UC-XXX) in a Spring Boot application: @Service classes with constructor injection, @Transactional boundaries, the business rules with UC-XXX BR-YYY markers, domain exceptions for every rejection the API or UI turns into a message, and Bean Validation on t…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- JavaDocs: transport: streamable-http; url: https://www.javadocs.dev/mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.