aiup-angular-jpa

AI Unified Process Marketplace

A collection of Claude Code plugins that automate the AI Unified Process (AIUP) — a structured workflow for taking a software project from raw vision to fully implemented, tested code, with requirements at the center at every step.

What is the AI Unified Process?

AI Unified Process is a disciplined AI-assisted development methodology where every project starts with a written vision, proceeds through requirements, an entity model, and use case specifications, and only then enters implementation. Nothing gets built without a use case. Nothing reaches production without tests traceable to requirements.

This prevents the common failure mode of AI-assisted development: jumping straight to code from a vague prompt, producing something that half-works and can't be maintained.

The methodology is based on the phases of the Rational Unified Process — Inception, Elaboration, Construction, Transition — but adapted for AI-driven workflows.

AIUP Workflow

Inception          Elaboration                          Construction
─────────────────  ──────────────────────────────────   ────────────────────────────────────────────────
/requirements  →  /entity-model  →  /use-case-diagram  →  /use-case-spec  →  /flyway-migration
                                                                          ↘  /implement
                                                                          ↘  /browserless-test
                                                                          ↘  /playwright-test

For an Angular/JPA project, the inception and elaboration parts look the same, as they are part of the aiup- core plugin. The construction, however, is optimized for tech stack SpringBoot with JPA and Angular in frontend. It tests the frontend with Angular vitest unittests, the backend with spring-boot integrations tests and the whole app with playwright e2e tests. Further it takes existing backend architecture, a hexagonal multi-module Maven reactor rather than a single flat module into consideration.

Inception          Elaboration                          Construction
─────────────────  ──────────────────────────────────   ────────────────────────────────────────────────
/requirements  →  /entity-model  →  /use-case-diagram  →  /use-case-spec  →  /flyway-migration
                                                                          ↘  /implement
                                                                          ↘  /spring-boot-test
                                                                          ↘  /vitest-test
                                                                          ↘  /playwright-test

Each skill picks up where the previous one left off using the files produced along the way (docs/vision.md, docs/requirements.md, docs/entity_model.md, docs/use_cases.puml, docs/use_cases/UC-*.md). At any point you can inspect or manually edit these files before continuing.

Inheriting a legacy codebase? Start with /reverse-engineer — it walks the existing code, configuration, and schema and produces the same docs/use_cases.puml, docs/use_cases/UC-*.md, and docs/entity_model.md artifacts the forward workflow would have produced, giving you a documented baseline to work from.

	Inception	Elaboration	Construction	Transition
aiup-core	/requirements	/entity-model /use-case-diagram	/use-case-spec
aiup-vaadin-jooq			/flyway-migration /implement /browserless-test /playwright-test
aiup-angular-jpa			/flyway-migration /implement /spring-boot-test /vitest-test /playwright-test

---

Prerequisites