CtrlK
BlogDocsLog inGet started
Tessl Logo
PluginPublic

ai-unified-process/aiup-flyway

AI Unified Process migration layer - Flyway schema migrations from the entity model

84

1.00x
Quality

91%

Does it follow best practices?

Impact

85%

1.00x

2 of 3 eval scenarios. Add 1 more for a full score.

SecuritybySnyk

Passed

No findings from the security scan

Overview
Quality
Evals
Security
Files

aiup-flyway

aiup-flyway is the AI Unified Process layer plugin for the migration layer: versioned Flyway SQL migrations derived from the entity model that aiup-core produces. It is one plugin of a layer combination; it does not build data access, services, or UI.

Skills

LayerSkillTest skillResult
Migration/flyway-schema–V*.sql scripts with sequences, tables, constraints, and foreign keys

The migration layer has no test skill: the persistence and service tests exercise the schema, and the test skills of those layers write the test data migrations.

How it is driven

aiup-core (3.0.0 or later) orchestrates the layer plugins:

/stack             → docs/architecture/stack.md records flyway-schema for the Migration layer
/use-case-implement UC-001      → flyway-schema → persistence → service → API → UI
/use-case-test UC-001           → the test skills of the other layers
/use-case-coverage UC-001       → the audit, using the Markers table of docs/architecture/stack.md

/use-case-implement runs /flyway-schema only when the use case needs a table, column, or constraint the schema does not have yet. Run directly, /flyway-schema UC-001 builds the migration layer of one use case, and /flyway-schema without an argument creates the tables of every entity the schema does not have yet.

Migrations go to the location the Migration row of docs/architecture/stack.md records — in a hexagonal reactor the persistence adapter module. A business rule the database enforces gets a -- UC-XXX BR-YYY: comment above its constraint, and the skill keeps its rows in the Markers table of docs/architecture/stack.md current.

Combinations

ProjectPlugins next to aiup-core
REST API, Spring Boot, jOOQaiup-flyway, aiup-jooq, aiup-spring-boot
REST API, Spring Boot, JPAaiup-flyway, aiup-jpa, aiup-spring-boot
Vaadin Flow, jOOQaiup-flyway, aiup-jooq, aiup-spring-boot, aiup-vaadin
Hilla, jOOQaiup-flyway, aiup-jooq, aiup-spring-boot, aiup-vaadin
Angular, Spring Boot, JPAaiup-flyway, aiup-jpa, aiup-spring-boot, aiup-angular, aiup-playwright

Do not combine the layer plugins with a combined stack plugin (aiup-vaadin-jooq, aiup-angular-jpa, aiup-blazor-dotnet, aiup-nestjs-nextjs); those ship their own migration skill — /flyway-migration in aiup-vaadin-jooq and aiup-angular-jpa, /ef-migration in aiup-blazor-dotnet, /drizzle-migration in aiup-nestjs-nextjs.

Installation

Tessl

tessl install ai-unified-process/aiup-core
tessl install ai-unified-process/aiup-flyway

Claude Code

/plugin marketplace add ai-unified-process/marketplace
/plugin install aiup-core
/plugin install aiup-flyway

See the marketplace installation guides for other agents and manual adoption.

MCP servers

None. Flyway's documentation is reachable through aiup-core's context7 server.

License

Apache-2.0 · © 2025-2026 Simon Martinelli and the AI Unified Process contributors

See LICENSE and NOTICE. "AI Unified Process" identifies the original methodology; derived works must retain the NOTICE file and must not present themselves as the official AI Unified Process.

Workspace
ai-unified-process
Visibility
Public
Created
Last updated
Publish Source
GitHub
Badge
ai-unified-process/aiup-flyway badge