ai-unified-process-marketplace
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 11 Nov 2026. Its scripts were only partly scanned.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/AI-Unified-Process/marketplace with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/AI-Unified-Process/marketplace'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/ai-unified-process--marketplace)HTML
<a href="/listings/ai-unified-process--marketplace"><img src="/api/listings/ai-unified-process--marketplace/badge.svg" alt="findsafeskills safety rating" /></a>Install
Install instructions from the README
As written by the repo's author. findsafeskills has not verified these steps.
Before installing AI Unified Process, create `docs/vision.md` in the target project. It should describe the mission, target users, goals, scope, and constraints. A copy-ready [vision template](docs/templates/vision.md) is available.
Claude Code
/plugin marketplace add ai-unified-process/marketplace /plugin install aiup-core /plugin install aiup-flyway /plugin install aiup-jooq /plugin install aiup-spring-boot
This example is a REST API with Spring Boot and jOOQ; install the layer plugins of your project, or one combined stack plugin instead.
Any supported agent through Tessl
tessl init --agent agents tessl install ai-unified-process/aiup-core tessl install ai-unified-process/aiup-flyway tessl install ai-unified-process/aiup-jooq tessl install ai-unified-process/aiup-spring-boot
Tessl installs versioned skills and maps each plugin's MCP servers (its bundled `.mcp.json`) into the configured agent layout. Replace `agents` with a host-specific identifier such as `claude-code`, `cursor`, `gemini`, `codex`, `copilot`, or `copilot-vscode` when you do not want the vendor-neutral layout.
Create the first artifacts
Run the core skills in the target project:
/requirements /entity-model /use-case-diagram /use-case-spec UC-001
Agents that do not expose skills as slash commands can invoke them by intent, for example: "Create the requirements catalog from `docs/vision.md`" or "Specify UC-001".
[Follow the complete getting-started guide →](docs/getting-started.md)
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
.claude-plugin/marketplace.json · Manifest · 85 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- {
- "name": "ai-unified-process-marketplace",
- "owner": {
- "name": "Simon Martinelli",
- "email": "simon@martinelli.ch",
- "url": "https://unifiedprocess.ai"
- },
- "plugins": [
- {
- "name": "aiup-core",
- "source": "./aiup-core",
- "description": "AI Unified Process core - stack-agnostic requirements, entity model, and use cases, plus the construction orchestrators for layer plugins"
- },
- {
- "name": "aiup-vaadin-jooq",
- "source": "./aiup-vaadin-jooq",
- "description": "Deprecated — use the layer plugins. AI Unified Process for the Vaadin/jOOQ stack - migrations, implementation, tests"
- },
- {
- "name": "aiup-angular-jpa",
- "source": "./aiup-angular-jpa",
- "description": "Deprecated — use the layer plugins. AI Unified Process for the Angular/JPA stack - migrations, implementation, tests"
- },
- {
- "name": "aiup-blazor-dotnet",
- "source": "./aiup-blazor-dotnet",
- "description": "AI Unified Process for the C# / Blazor .NET 10 stack - migrations, implementation, tests"
- },
- {
- "name": "aiup-nestjs-nextjs",
- "source": "./aiup-nestjs-nextjs",
- "description": "Deprecated — use the layer plugins. AI Unified Process for the NestJS/Drizzle + Next.js stack - migrations, implementation, tests"
- },
- {
- "name": "aiup-flyway",
- "source": "./aiup-flyway",
- "description": "AI Unified Process migration layer - Flyway schema migrations from the entity model"
- },
- {
- "name": "aiup-jooq",
- "source": "./aiup-jooq",
- "description": "AI Unified Process persistence layer - jOOQ repositories, projections, and repository tests"
- },
- {
- "name": "aiup-jpa",
- "source": "./aiup-jpa",
- "description": "AI Unified Process persistence layer with Spring Data JPA - entities, repositories, and repository tests"
- },
- {
- "name": "aiup-spring-boot",
- "source": "./aiup-spring-boot",
- "description": "AI Unified Process Spring Boot layers - service, REST API, and external system client implementation and tests"
- },
- {
- "name": "aiup-vaadin",
- "source": "./aiup-vaadin",
- "description": "AI Unified Process UI layer with Vaadin - Flow and Hilla views, Browserless and Vitest view tests, and Playwright end-to-end tests"
- },
- {
- "name": "aiup-angular",
- "source": "./aiup-angular",
- "description": "AI Unified Process UI layer for Angular - standalone components, signals, HttpClient services, Vitest component tests"
- },
- {
- "name": "aiup-playwright",
- "source": "./aiup-playwright",
- "description": "AI Unified Process end-to-end layer - Playwright browser tests for use cases and test case journeys of any web UI"
- },
- {
- "name": "aiup-drizzle",
- "source": "./aiup-drizzle",
- "description": "AI Unified Process migration and persistence layers - Drizzle ORM schema, generated PostgreSQL migrations, repositories, and their tests"
- },
- {
- "name": "aiup-nestjs",
- "source": "./aiup-nestjs",
- "description": "AI Unified Process service and API layers - NestJS services, REST controllers, and their tests"
- },
- {
- "name": "aiup-nextjs",
- "source": "./aiup-nextjs",
- "description": "AI Unified Process UI layer - Next.js App Router pages on an API layer, and their component tests"
- }
- ]
- }
README.md · README · 310 lines
View this file on GitHub (read at the repository's current version: the scan did not record which commit it read)
This file has changed since it was scanned, so this is not exactly the text that was scanned, and no line is marked. The findings are listed with the safety scan above.
- <!--
- Copyright 2025-2026 Simon Martinelli and the AI Unified Process contributors.
- Part of the AI Unified Process — https://unifiedprocess.ai
- Licensed under the Apache License, Version 2.0. See LICENSE and NOTICE.
- -->
- # AI Unified Process Marketplace
- AI Unified Process is a requirements-first workflow for taking software from a product vision to reviewed
- specifications, implementation, and traceable tests. This repository distributes the workflow as portable Agent
- Plugins and Agent Skills for Claude Code, OpenAI Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, and other
- compatible coding agents.
- [Get started](docs/getting-started.md) · [Understand the workflow](docs/workflow.md) ·
- [Choose a plugin](#choose-your-plugins) · [Installation guides](#installation)
- ## Why AI Unified Process?
- AI-assisted development often jumps from a vague prompt directly to code. AI Unified Process inserts durable,
- human-reviewable artifacts between intent and implementation:
- - requirements with stable identifiers;
- - an explicit domain entity model;
- - use cases that define user goals and behavior;
- - test journeys that trace back to those use cases;
- - stack-specific implementation and tests built from the reviewed specifications;
- - a user guide, an acceptance protocol, and release notes derived from those same specifications.
- The workflow is inspired by the phases of the
- [Rational Unified Process](https://en.wikipedia.org/wiki/Rational_unified_process), adapted for coding agents and
- plain-text artifacts that live with the source code.
- ## Workflow
- ```text
- Inception Elaboration Construction Transition
- ───────────── ────────────────────────────────────────── ──────────────────────────────────────────── ──────────────────────
- /requirements → /entity-model → /stack → /use-case-diagram → /use-case-spec → implement → test → coverage → /acceptance-protocol
- ↘ /business-process /test-case → automate the journey /user-guide
- (optional) /release-notes
- /spec-review at any point, /next names the next step
- ```
- `aiup-core` owns the stack-independent path from vision to specifications. Construction continues either with
- layer plugins — one per technology, combined per project — or with one combined stack plugin (`aiup-blazor-dotnet`; the others are deprecated). With layer plugins, run
- `/stack` once; then *implement*, *test*, and *coverage* are `/use-case-implement`, `/use-case-test`, and
- `/use-case-coverage`, and *automate the journey* is `/test-case-implement`. A combined stack plugin uses its own
- `/implement`, test skills, and `/coverage-check` where it ships one.
- Transition hands the system over: `/acceptance-protocol` runs the user acceptance round from the test cases and sets
- the accepted use cases to `Done`, `/user-guide` writes the user guide from the use cases at `Tested` or `Done`, and
- `/release-notes` lists what reached `Done` since the last release.
- Each step reads the files produced by earlier steps. You can review or edit an artifact before continuing, and every
- later result remains traceable to the corresponding requirement or use case.
- [Read about phases, artifacts, traceability, and change handling →](docs/workflow.md)
- ### Automated construction
- The Werkstatt is a GitHub Actions workflow that builds the `Approved` use cases of a change branch through the same
- skills: specification lint, implementation, tests, build, coverage audit, and fix rounds. Its result is one pull
- request against the change branch, in which every finished use case has moved to `Tested`; a use case with a blocking
- open question stays `Approved` and keeps only its questions. The same stations also run on your own machine with
- `pipelines/werkstatt/run-local.sh`, in a worktree of their own and without a pull request.
- [Read how to set up and run the Werkstatt →](docs/werkstatt.md)
- ## Choose your plugins
- Install `aiup-core` in every project. For construction, combine **layer plugins** — one per technical layer — or add
- exactly one **combined stack plugin**. Do not mix both in one project. Of the combined stack plugins, only
- `aiup-blazor-dotnet` is maintained; the others are deprecated.
- ### Layer plugins
- Pick one plugin per layer the project has. `/stack` records the combination in the stack file,
- `docs/architecture/stack.md`; `/use-case-implement UC-001` runs the layer skills bottom-up, `/use-case-test UC-001` writes
- the tests from the integration layer up — from the entry layer the use case is offered through, the first layer whose
- tests run in process against the real database, so the layers below need no tests of their own
- (that API still gets its own contract tests when the use case is offered through it) — and `/use-case-coverage UC-001`
- audits the result. A use case offered through only some entry
- points (an administration screen without an API) says so in its `**Layers:**` line, and only those layers are built
- and tested. Optional `**Mockup:**` and `**API:**` lines link the screen designs the UI layer takes its layout from
- and the operations of an API contract agreed with a partner system, which the API layer builds as written.
- | Plugin | Layer | Skills |
- |-----------------------------------------|-----------------------|----------------------------------------------------------------------------------------------|
- | [`aiup-flyway`](aiup-flyway/) | Migration | `/flyway-schema` |
- | [`aiup-jooq`](aiup-jooq/) | Persistence | `/jooq-persistence`, `/jooq-persistence-test` |
- | [`aiup-jpa`](aiup-jpa/) | Persistence | `/jpa-persistence`, `/jpa-persistence-test` |
- | [`aiup-spring-boot`](aiup-spring-boot/) | Service, REST API, Client | `/spring-service`, `/spring-rest`, `/spring-client`, `/spring-service-test`, `/spring-rest-test`, `/spring-client-test` |
- | [`aiup-vaadin`](aiup-vaadin/) | UI (Flow, Hilla), E2E | `/vaadin-flow-ui`, `/hilla-ui`, `/vaadin-flow-ui-test`, `/hilla-ui-test`, `/vaadin-e2e-test` |
- | [`aiup-angular`](aiup-angular/) | UI | `/angular-ui`, `/angular-ui-test` |
- | [`aiup-playwright`](aiup-playwright/) | E2E (TypeScript) | `/playwright-e2e-test` |
- | [`aiup-drizzle`](aiup-drizzle/) | Migration, Persistence | `/drizzle-schema`, `/drizzle-persistence`, `/drizzle-persistence-test` |
- | [`aiup-nestjs`](aiup-nestjs/) | Service, REST API | `/nest-service`, `/nest-rest`, `/nest-service-test`, `/nest-rest-test` |
- | [`aiup-nextjs`](aiup-nextjs/) | UI | `/nextjs-ui`, `/nextjs-ui-test` |
- | Project | Plugins next to `aiup-core` |
- |-----------------------------|----------------------------------------------------------------------------------|
- | REST API, Spring Boot, jOOQ | `aiup-flyway`, `aiup-jooq`, `aiup-spring-boot` |
- | REST API, Spring Boot, JPA | `aiup-flyway`, `aiup-jpa`, `aiup-spring-boot` |
- | Vaadin Flow or Hilla, jOOQ | `aiup-flyway`, `aiup-jooq`, `aiup-spring-boot`, `aiup-vaadin` |
- | Vaadin Flow and a REST API | `aiup-flyway`, `aiup-jooq`, `aiup-spring-boot`, `aiup-vaadin` |
- | Angular, Spring Boot, JPA | `aiup-flyway`, `aiup-jpa`, `aiup-spring-boot`, `aiup-angular`, `aiup-playwright` |
- | REST API, NestJS, Drizzle | `aiup-drizzle`, `aiup-nestjs` |
- | Angular, NestJS, Drizzle | `aiup-drizzle`, `aiup-nestjs`, `aiup-angular`, `aiup-playwright` |
- | Next.js, NestJS, Drizzle | `aiup-drizzle`, `aiup-nestjs`, `aiup-nextjs`, `aiup-playwright` |
- | Next.js, Spring Boot, JPA | `aiup-flyway`, `aiup-jpa`, `aiup-spring-boot`, `aiup-nextjs`, `aiup-playwright` |
- ### Combined stack plugins
- | Plugin | Stack and responsibility | Construction skills |
- |---------------------------------------------|-----------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------|
- | [`aiup-vaadin-jooq`](aiup-vaadin-jooq/) | Vaadin Flow or Hilla with jOOQ (deprecated) | Flyway, implementation, Browserless or Karibu, Playwright, coverage check |
- | [`aiup-angular-jpa`](aiup-angular-jpa/) | Angular with Spring Boot and JPA (deprecated) | Flyway, implementation, Spring Boot tests, Vitest, Playwright, coverage check |
- | [`aiup-blazor-dotnet`](aiup-blazor-dotnet/) | C# and Blazor on .NET 10 with EF Core | EF migrations, Vertical Slices, bUnit, xUnit, Playwright |
- | [`aiup-nestjs-nextjs`](aiup-nestjs-nextjs/) | NestJS and Drizzle with Next.js (deprecated) | Drizzle migrations, implementation, Vitest, Supertest, React Testing Library, Playwright |
- The coverage audit belongs to `aiup-core`: `/use-case-coverage` and `/test-case-coverage` run the read-only
- [`uc-coverage-layered`](aiup-core/agents/uc-coverage-layered.md) sub-agent on demand. It reports which parts of the
- specification have no code or no test behind them, and which code has no specification behind it, and judges
- implementation and tests together, and with `html` saves the report as a page under `docs/coverage/`; `/use-case-test` and `/test-case-implement` end by handing off to it rather than
- running it themselves, so a construction round stays fast. Of the combined stack plugins, the deprecated
- `aiup-vaadin-jooq` and `aiup-angular-jpa` have their own `/coverage-check`; `aiup-blazor-dotnet` and the deprecated
- `aiup-nestjs-nextjs` have no audit.
- `aiup-vaadin-jooq`, `aiup-angular-jpa`, and `aiup-nestjs-nextjs` are deprecated in favour of the layer plugins and
- will be removed with `aiup-core` 4.0.0. The [migration guide](docs/migration.md) walks an existing project through the switch.
- `aiup-blazor-dotnet` stays a combined plugin: its Vertical Slice Architecture keeps a use case's handler and data
- access together in one slice, which horizontal layer plugins would split apart.
- `aiup-core` itself ships `/requirements`, `/entity-model`, `/use-case-diagram`, `/use-case-spec`, `/business-process`,
- `/test-case`, `/spec-review`, `/next`, `/open-questions`, `/architecture-decision`, `/reverse-engineer`, for the
- Transition phase `/user-guide`, `/acceptance-protocol`, and `/release-notes`, and, for layer plugins, `/stack`,
- `/use-case-implement`, `/use-case-test`, `/use-case-coverage`, `/test-case-implement`, and `/test-case-coverage`.
- Use only `aiup-core` when working with another implementation stack. The methodology ends at a documented boundary,
- so the specifications can feed a custom implementation workflow.
- ## Quick start
- Before installing AI Unified Process, create `docs/vision.md` in the target project. It should describe the mission, target users,
- goals, scope, and constraints. A copy-ready [vision template](docs/templates/vision.md) is available.
- ### Claude Code
- ```text
- /plugin marketplace add ai-unified-process/marketplace
- /plugin install aiup-core
- /plugin install aiup-flyway
- /plugin install aiup-jooq
- /plugin install aiup-spring-boot
- ```
- This example is a REST API with Spring Boot and jOOQ; install the layer plugins of your project, or one combined
- stack plugin instead.
- ### Any supported agent through Tessl
- ```sh
- tessl init --agent agents
- tessl install ai-unified-process/aiup-core
- tessl install ai-unified-process/aiup-flyway
- tessl install ai-unified-process/aiup-jooq
- tessl install ai-unified-process/aiup-spring-boot
- ```
- Tessl installs versioned skills and maps each plugin's MCP servers (its bundled `.mcp.json`) into the configured agent
- layout.
- Replace `agents` with a host-specific identifier such as `claude-code`, `cursor`, `gemini`, `codex`, `copilot`, or
- `copilot-vscode` when you do not want the vendor-neutral layout.
- ### Create the first artifacts
- Run the core skills in the target project:
- ```text
- /requirements
- /entity-model
- /use-case-diagram
- /use-case-spec UC-001
- ```
- Agents that do not expose skills as slash commands can invoke them by intent, for example: "Create the requirements
- catalog from `docs/vision.md`" or "Specify UC-001".
- [Follow the complete getting-started guide →](docs/getting-started.md)
- ## Generated artifacts
- The stack-independent workflow creates a shared documentation contract:
- ```text
- docs/
- ├── vision.md # maintained by the team
- ├── requirements.md # /requirements
- ├── glossary.md # /requirements (domain terms and synonyms to avoid)
- ├── entity_model.md # /entity-model
- ├── use_cases.puml # /use-case-diagram
- ├── processes/
- │ └── BP-001-*.bpmn # /business-process (optional), read by /test-case
- ├── use_cases/
- │ └── UC-001-*.md # /use-case-spec
- ├── test_cases/
- │ └── TC-001-*.md # /test-case
- ├── open_questions.md # /open-questions and the skills that find a gap (created with the first question)
- ├── user_guide/ # /user-guide: one chapter per actor, from the use cases at Tested or Done
- ├── acceptance/
- │ └── release-1.4.md # /acceptance-protocol: one protocol per acceptance round
- ├── release-notes.md # /release-notes: what reached Done, newest version first
- └── architecture/
- ├── stack.md # /stack (layer plugins only): layer → technology → skill → test skill
- └── decisions/
- └── ADR-001-*.md # /architecture-decision, each linked to the NFRs and constraints it serves
- ```
- Stack plugins consume these files and place generated code and tests according to the conventions of the target
- project. Their READMEs document the supported layouts and exact prerequisites.
- ## Existing applications
- Start an undocumented application with:
- ```text
- /reverse-engineer
- ```
- The skill inspects entry points, domain models, schema, authentication, and integrations, then proposes an entity
- model, use case diagram, and individual use case specifications. It reports behavior it cannot classify so the team
- can review gaps before adopting the result as a baseline.
- ## Installation
- - [Claude Code](docs/installation/claude-code.md) — add the marketplace and install plugins directly.
- - [Tessl](docs/installation/tessl.md) — install pinned plugins for one or more supported agents.
- - [Agent Plugins and manual setup](docs/installation/other-agents.md) — direct packages, skill locations, MCP examples,
- and host-specific caveats.
- Every plugin directory contains:
- - a Claude Code manifest and MCP configuration;
- - an Agent Plugins v1.0.0 `plugin.json` and `mcp.json`;
- - portable Agent Skills under `skills/`;
- - sub-agent definitions under `agents/`, where the plugin ships one;
- - a Tessl package manifest;
- - evaluation scenarios used during publication.
- CI keeps the three plugin manifest formats and their MCP definitions in sync, and verifies that every
- skill and document carries its copyright header and that each plugin ships `LICENSE` and `NOTICE`.
- ## Documentation
- | Guide | Contents |
- |--------------------------------------------------------------|----------------------------------------------------------------------------------------------|
- | [Getting started](docs/getting-started.md) | Select plugins, prepare a vision, install AI Unified Process, and create the first artifacts |
- | [Workflow and artifacts](docs/workflow.md) | Phases, traceability, artifact ownership, changes, and legacy projects |
- | [Migration guide](docs/migration.md) | Moving a project from a deprecated combined stack plugin to the layer plugins |
- | [Werkstatt](docs/werkstatt.md) | Building the approved use cases of a change branch in GitHub Actions or on your machine |
- | [Werkstatt architecture](docs/werkstatt-architecture.md) | The concept behind the Werkstatt: stations, gates, and the andon cord |
- | [Generation workflow versioning](docs/generate-workflow-versioning.md) | For maintainers: how the shared workflows are released behind the `v1` tag |
- | [Project setup](docs/guides/project-setup.md) | Recommended project documentation tree and agent guidance |
- | [Writing a layer skill](docs/guides/layer-skill.md) | The contract a team's own layer skill fulfils to run under `/use-case-implement` |
- | [Vision template](docs/templates/vision.md) | Starting point for `docs/vision.md` |
- | [CLAUDE.md template](docs/templates/CLAUDE.md) | Stack-neutral repository instructions for Claude Code |
- | [Complete tutorial](https://unifiedprocess.ai/tutorial.html) | Book Library example: stack-neutral analysis, then construction with the deprecated `aiup-vaadin-jooq`; use the layer plugins and the migration guide instead |
- Detailed skill behavior is documented in each plugin's `skills/*/SKILL.md`. Those files are the authoritative source
- for inputs, outputs, safety constraints, and execution steps; READMEs provide navigation and concise summaries.
- ## Repository layout
- ```text
- marketplace/
- ├── aiup-core/
- ├── aiup-vaadin-jooq/
- ├── aiup-angular-jpa/
- ├── aiup-blazor-dotnet/
- ├── aiup-nestjs-nextjs/
- ├── aiup-drizzle/
- ├── aiup-nestjs/
- ├── aiup-nextjs/
- ├── aiup-flyway/
- ├── aiup-jooq/
- ├── aiup-jpa/
- ├── aiup-spring-boot/
- ├── aiup-vaadin/
- ├── aiup-angular/
- ├── aiup-playwright/
- ├── docs/
- ├── pipelines/
- └── scripts/
- ```
- ## Learn more
- Visit [unifiedprocess.ai](https://unifiedprocess.ai) for the broader methodology.
- ## License
- Licensed under the [Apache License 2.0](LICENSE).
- ## Copyright and trademark
- Copyright 2025-2026 Simon Martinelli and the AI Unified Process contributors. The skills and documentation
- are licensed under Apache 2.0. "AI Unified Process" identifies the original methodology by Simon Martinelli
- ([unifiedprocess.ai](https://unifiedprocess.ai)). You may fork and modify this work under the license terms,
- but derived works must keep the [NOTICE](NOTICE) file and may not present themselves as the official
- AI Unified Process. If you build on it, please say so and link to this repository.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.