A Claude Code marketplace handles the AI Unified Process (AIUP) workflow end-to-end. An IDE plugin keeps the resulting specs and tests connected as you code. And AI Unified Studio gives every stakeholder a view of the project — straight from the Git repository.
A marketplace of Claude Code plugins designed to drive the AI Unified Process workflow: gathering requirements, modeling entities, specifying use cases, and generating implementation and tests.
Includes the stack-agnostic aiup-core plugin and four technology-specific plugins: aiup-vaadin-jooq for Vaadin + jOOQ applications, aiup-angular-jpa for Angular + Spring Boot JPA applications, aiup-blazor-dotnet for C# + Blazor applications on .NET 10, and aiup-nestjs-nextjs for NestJS + Next.js applications.
The AI Unified Process Navigator is a standalone IDE plugin, available for IntelliJ and Visual Studio Code, that links @UseCase annotated test methods to their UC-XXX-*.md specifications via gutter icons, and back from the spec to the test.
Works independently of Claude Code, but pairs naturally with the marketplace plugins: generate specs and tests with Claude Code, then traverse them inside your IDE.
A web-based workspace that gives all stakeholders a view of projects following the AI Unified Process: structured editors for requirements, entity models, and use case specifications, with diagrams generated automatically.
All artifacts live in your Git repository on GitHub or Bitbucket — the same files the plugins produce and consume, with no conversion. Currently in private beta — access by invitation.
A stack-agnostic core for requirements engineering, paired with technology-specific plugins for Vaadin + jOOQ, Angular + JPA, and Blazor + .NET implementation.
Stack-agnostic methodology plugin with templates for requirements-driven development. Works with any technology stack.
/requirements
– Create requirements catalog
/entity-model
– Create entity model with ER diagrams
/use-case-diagram
– Generate PlantUML use case diagram
/use-case-spec
– Write use case specification
/reverse-engineer
– Reverse-engineer existing project into AI Unified Process artifacts
Technology-specific plugin for Java web application development combining Vaadin UI framework with jOOQ type-safe database access.
/flyway-migration
– Create Flyway database migration
/implement
– Implement use case with Vaadin + jOOQ
/browserless-test
– Create Vaadin Browserless unit tests
/playwright-test
– Create Playwright E2E tests
Technology-specific plugin for a split client/server architecture: a Spring Boot + JPA backend (flat or hexagonal multi-module) with an Angular frontend.
A special thank you to Marc Affolter for contributing this plugin.
/flyway-migration
– Create Flyway database migration
/implement
– Implement use case with Spring Boot + Angular
/spring-boot-test
– Create Spring Boot API tests
/vitest-test
– Create Vitest component tests for Angular
/playwright-test
– Create Playwright E2E tests
Technology-specific plugin for C# and Blazor on .NET 10: EF Core data access and Blazor components, implemented in a Vertical Slice Architecture.
A special thank you to Carl J. Mosca for contributing this plugin.
/ef-migration
– Create EF Core database migration
/implement
– Implement use case with C# + Blazor
/bunit-test
– Create bUnit component tests for Blazor
/dotnet-test
– Create backend unit and integration tests
/playwright-test
– Create Playwright E2E tests
Technology-specific plugin for a TypeScript-native split client/server architecture: a NestJS backend with Drizzle ORM over PostgreSQL and a Next.js App Router frontend.
A special thank you to Swift Ugandan for contributing this plugin.
/drizzle-migration
– Create Drizzle schema and SQL migration
/implement
– Implement use case with NestJS + Next.js
/nest-test
– Create NestJS backend tests with Vitest
/react-test
– Create Vitest component tests for Next.js
/playwright-test
– Create Playwright E2E tests
More technology-specific plugins are in development. Contributions are welcome! Add your own plugins to help the community.
Today's plugins automate individual steps that you invoke one command at a time. We are working on automating the AI Unified Process end-to-end, so that the chain from requirements to tests runs with far fewer manual command invocations.
Get started with the Claude Code marketplace plugins in just a few steps
Agent Skills (SKILL.md) is now an open standard, and every plugin also conforms to the Agent Plugins packaging standard (agent-plugins.org). The same skill files in this marketplace run natively — with auto-triggering by description — in OpenAI Codex CLI, Cursor, GitHub Copilot, Gemini CLI, and OpenCode. Install them with Tessl, load them with any Agent Plugins client, or clone the repo, drop the skill folders into your tool's skills directory, and configure the MCP servers.
Tessl is an agent-agnostic package manager for skills: it installs versioned skills and wires the MCP servers into the correct per-agent directory for whichever coding agent it detects. All plugins are published to the Tessl registry as ai-unified-process/aiup-core, ai-unified-process/aiup-vaadin-jooq, ai-unified-process/aiup-angular-jpa, ai-unified-process/aiup-blazor-dotnet, and ai-unified-process/aiup-nestjs-nextjs.
Installed plugins land in .tessl/plugins/ and are tracked in tessl.json, so versions are pinned and reproducible across your team.
Every plugin directory is also a conformant Agent Plugins package — the open, vendor-neutral plugin standard governed by a steering committee with representatives from Amazon, Cursor, Microsoft, OpenAI, and Vercel. Each plugin ships the standard's plugin.json and mcp.json manifests alongside the Claude Code ones.
Any client that implements Agent Plugins can load a plugin straight from a checkout of the marketplace repository — skills and MCP servers included, no conversion needed.
Clone the marketplace repo, then copy or symlink the skill folders into your tool's skills directory and configure the MCP servers from each plugin's .mcp.json in your tool's MCP config.
Trigger skills the same way you would in Claude Code — say "write requirements" or invoke /requirements. The file outputs are identical regardless of tool, so the chain composes even if you mix tools across steps.
Native SKILL.md support — drop into ~/.codex/skills/ or .agents/skills/.
Native Agent Skills since Cursor 2.4 — drop into project-local .cursor/skills/.
Understands Claude Code's /plugin marketplace commands directly — install the plugins the same way as in Claude Code, skills and MCP included.
Native SKILL.md support — drop into .gemini/skills/ or ~/.gemini/skills/.
Native skill support — also scans .claude/skills/ and .agents/skills/, so skills installed for Claude Code are picked up without copying.
A separate IDE plugin for IntelliJ and Visual Studio Code that links use case specifications to their tests, independent of Claude Code
Click the gutter icon on a @UseCase annotated test method to jump to its matching UC-XXX-*.md specification, and back again from the spec header to the test.
Markdown headers and business rule references in your specs become clickable, keeping requirements and tests in sync as you work.
In IntelliJ IDEA, go to Settings → Plugins → Marketplace; in Visual Studio Code, open the Extensions view. Search for "AI Unified Process Navigator" and click Install. No Claude Code required.
Open source under Apache License 2.0. Works with IntelliJ IDEA and other JetBrains IDEs as well as Visual Studio Code.
Workshops, consulting, and tailored rollouts of the AI Unified Process. Book a call to talk through how the AI Unified Process fits your stack and team.