scenario-to-activity-v1

Generate UML activity diagrams from business scenarios with a temporary domain model.

Updated Feb 19, 2026
One-click install
npx skills add https://github.com/atanaka/uml-workflow-v3 --skill scenario-to-activity-v1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scenario-to-activity-v1
Source: https://github.com/atanaka/uml-workflow-v3/tree/main/skills/scenario-to-activity-v1
Command: npx skills add https://github.com/atanaka/uml-workflow-v3 --skill scenario-to-activity-v1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill helps teams automatically transform rich business scenarios into visual UML activity diagrams by generating a temporary domain model during analysis, eliminating the need for an existing class diagram in early-stage design.

Core Features & Use Cases

  • Multi-language input/output with automatic language detection (Japanese/English/Bilingual)
  • Internal temporary domain model creation (no pre-existing class diagrams required)
  • Structured outputs including a PlantUML activity diagram plus artifacts like a business scenario document and activity data JSON

Quick Start

Provide a rich business overview and scenario with steps to generate an activity diagram and temporary domain model.

Frequently Asked Questions about scenario-to-activity-v1

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a UML activity diagram from a business scenario without an existing class diagram?

To generate a UML activity diagram without an existing class diagram, provide a rich business overview with scenarios, rules, and stakeholders. The Skill constructs a temporary domain model during analysis to produce the PlantUML diagram.

Can I create PlantUML activity diagrams from bilingual business requirements?

Yes, you can create PlantUML activity diagrams from bilingual business requirements. The Skill features automatic language detection to support Japanese, English, and bilingual inputs and outputs natively.

What inputs do I need to provide for scenario analysis to produce an activity diagram?

For scenario analysis to produce an activity diagram, provide end-to-end workflow inputs including an overview, scenarios, rules, glossary, stakeholders, and non-functional requirements. These rich inputs drive the temporary domain model generation.

What artifacts are generated alongside the PlantUML diagram during scenario analysis?

During scenario analysis, the generated artifacts include a temporary domain model, a business scenario document, and activity data JSON alongside the PlantUML diagram. These structured outputs provide comprehensive documentation of the workflow.

Does this approach require a pre-existing domain model to map end-to-end workflows?

No, this approach does not require a pre-existing domain model to map end-to-end workflows. The Skill automatically constructs a temporary domain model during analysis, eliminating the need for early-stage class diagrams.