Maintaining specifications with scattered tools — Word for the vision, Excel for requirements, separate UML tools for diagrams — leads to media breaks, poor versioning, and inconsistent artifacts. The Studio replaces them with one workspace on top of your Git repository.
Business analysts capture the vision and requirements, requirements engineers specify use cases and the entity model, software and test engineers read the specifications and add technical detail — all in the same tool, on the same Git-versioned files.
Project leads see status and progress at a glance, without opening a single Markdown file.
Each artifact type gets a dedicated editor with validation instead of a blank text file. ER diagrams are generated from the entity model, and activity diagrams from use case scenarios — automatically, live in the browser.
Nobody needs to write PlantUML or Mermaid by hand; the diagrams can never drift out of sync with the specification.
From the project overview to the individual use case specification — the screenshots follow the Spring PetClinic example project.
The home view shows all use cases of the project, grouped by functional area, with their status and the overall progress. Every stakeholder sees where the project stands at a glance — no repository checkout, no Markdown reading required.
The files view navigates the repository directly: browse the docs folder, create, rename, move, or delete files and directories. Every operation is written back as a Git commit with a traceable message and author — the repository stays the single source of truth.
Entities, attributes, and relationships are maintained in a structured editor — no diagram drawing, no syntax to learn. The Mermaid ER diagram is generated from the structured data and rendered live; the result is saved as a plain Markdown file (docs/entity_model.md) in the repository.
The use case diagram (docs/use_cases.puml) is edited as PlantUML source with syntax highlighting and a live preview next to it. A first draft of actors and use cases can be generated AI-assisted from the requirements catalog and then refined manually.
Each use case is maintained in a structured form following the AIUP format: overview, preconditions, main success scenario, alternative flows, postconditions, and business rules. The activity diagram is generated automatically from the scenarios — here UC-009 "Book Visit for Pet" with its alternative flows.
The traceability view shows, per use case, whether implementing code and tests exist in the repository — and whether that matches the maintained status. It reads the same @UseCase convention as the AIUP Navigator IDE plugin, so the specification, implementation, and tests stay verifiably connected.
Users sign in with their Git account — no separate credentials. Administrators connect the organization, configure repositories, and manage team roles.
Connect your GitHub organization or account by installing the AIUP Studio app. The Studio accesses the released repositories with short-lived installation tokens — independent of individual user accounts.
Configure one or more repositories per tenant: Git provider, branch, and write strategy — commit directly to the branch or work through pull requests for protected branches.
Manage the users of your tenant: assign the roles Administrator, Editor, or Reader, invite new team members, and set the default role for first-time sign-ins. Invited users join with their Git account — no separate registration.
The Studio reads and writes exactly the artifact formats of the aiup-core skills — the same files the Claude Code plugins produce and consume.
A repository reverse-engineered with /reverse-engineer opens in the Studio without any conversion — and use case specifications written in the Studio feed directly into /implement and the test commands of the stack plugins.
Code and test generation stay where they belong: in your AI coding tool, working on the same Git repository.
The Claude Code marketplace plugins drive the AIUP workflow from requirements to tests, and the AIUP Navigator IDE plugin links test methods to their use case specifications.
AIUP Studio is currently in private beta and not publicly available yet. Leave your email address and we'll send you an invitation as soon as your access is ready — your free trial starts with the invitation.
We onboard new teams in small batches and personally — no waiting list limbo, no spam.
AIUP Studio is in private beta — request an invitation above, or book a call to talk through how AIUP Studio fits your team.
