- Home
- Skills
- Agents & Orchestration
- rup-flow Pro: Complete RUP Workflow, Both Ways
More screenshots
Works with the AI Agents you already use
rup-flow Pro: Complete RUP Workflow, Both Ways
The complete RUP workflow for any AI coding agent: ranked domain model, 14 diagram types, design, traceability, code in both directions, themes and an interactive explorer.
$19
rup-flow Pro: Complete RUP Workflow, Both Ways
Example session with this skill installed
Use rup-flow-pro to reverse engineer src/ into docs/rup, in English. Then add the use case cancelOrder and check that the code and the documentation still agree.
- Read your context and instructions
- Compiled the rup-flow pro
Summary
Documented the NestJS service in src/ into docs/rup (English, PlantUML, default palette). 11 entities, 6 use cases, 14 business rules. Every claim marked
observed carries its path:line; 3 rules could not be read from the code and are open questions. check reports 0 errors and 2 warnings.
What was generated
| Discipline | Artifacts | Provenance |
|---|---|---|
| Domain model | Ranked model (4 levels), Order lifecycle | observed (9), assumed (2) |
| Requirements | Actors, RF/RNF, 6 use-case cards with specification and wireframes | observed + assumed |
| Analysis and design | Collaboration and sequence per use case, data model, components | observed |
| Quality | Traceability (6 rows), project profile, open questions | confirmed |
Drift found
| Kind | Where | Detail |
|---|---|---|
| Code ahead | src/orders/orders.service.ts:88 | Orders above 500 are held for review; no use case describes it |
| Model ahead | UC-004 shipOrder | Documented, no handler found |
| Conflict | RN-002 | Documentation: stock checked at checkout. Code: checked at payment (payments.service.ts:41) |
Open questions
- Is payment captured while placing the order or afterwards? (blocks UC-001)
- Who may cancel an order that is already packed? (blocks UC-003)
- Is the 500 threshold a rule or a test value? (
orders.service.ts:88)
Checks not executed
Visual inspection of the rendered SVGs; the project's test suite (no database available in this session).
Next steps
- Answer the three questions so the rules can move from open to confirmed
- Say "Implement UC-003 from the design" to generate code, tests and trace links
- Open
docs/rup/explorer.htmlto browse every diagram and trace relations





Connects securely to your tools. The creator never sees your data.
About this skill
The complete version of rup-flow. The free edition documents the first disciplines. Pro takes the same project all the way: models you can trust, code that traces back to them, and documentation that stays honest as the code changes. It works with Claude, Codex, Gemini, Cursor, Copilot, Windsurf, Cline and any agent with a shell.
What you get
- Every discipline, one structure. Ranked domain model with attributes and multiplicities, entity lifecycles, use-case diagrams (general and per actor), wireframes, analysis collaborations, design (classes, sequences, data model, components, deployment), implementation cards, code map, project profile, traceability, audit and decision records.
- Code in both directions. Reverse engineer a code base into documentation with every claim cited as
path:line; generate code, tests and@ruptrace links from reviewed models; detect drift between documentation and code. - Diagrams that look designed. Eight palettes or your own colors and fonts, Mermaid as a second language, PNG previews.
- An interactive explorer. One file, no server: an overview with a thumbnail of every diagram, search across all of them, relation tracing, light and dark, export to SVG and PNG.
- Stack pack: NestJS + Prisma + Jest. Layout, naming, error handling, persistence mapping and test patterns.
- Domain library: learning platforms (LMS). A ready ranked model, actors, use cases and the questions to ask before using it.
- Two subagents.
rup-architectgenerates;rup-revieweraudits independently and read-only. - A complete example project, so you can read the output before you use it.
It never makes things up
Every statement is marked confirmed, observed in code, assumed or open. Unknown business rules become questions, not invented requirements. The agent reports what it could not build or run.
Versioned and documented
Every release is versioned (rup-flow-pro-1.0.1) and states the free version it contains. Full documentation, with every command and artifact: https://hector-ae21.github.io/rup-flow-docs/
Requirements
Node.js 18+. Docker is optional. No other dependencies, no telemetry, no accounts. Everything runs on your machine.
Requires Node.js 18+. Diagram rendering requires Docker or a PlantUML server. Traceability requires manual resolution of 'open' questions.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 29 days ago
Requires
Permissions
File Scopes
Reads your code folder (read-only) when reverse engineering, and writes only inside the documentation folder you choose plus rup.config.json. Diagram sources are sent only to a PlantUML server running locally in Docker (127.0.0.1:8085). Docker pulls the public PlantUML and Mermaid images the first time. No telemetry, no accounts.