up-4-mapping-use-cases
Finds the use cases a system needs and records them as the use case diagram (docs/use_cases.puml, PlantUML): builds the actor-goal list from the requirements catalog, tests every candidate for user-goal level (one actor, one sitting), aggregates and splits Manage-X use cases, moves multi-role or waiting flows to a business process, checks that every functional requirement is realized and every actor connected, and proposes the delivery order of first slices. Use when the user asks which use cases exist or are missing, whether something is a use case at all or only a step of one, wants a use case diagram or overview, an actor-goal list, to split or merge use cases, to decide scope with an in/out list, or to check requirement-to-use-case coverage. Not for writing the steps of one use case, not for sorting use cases into bounded contexts or teams, and not for draw.io diagrams.
Pinned to revision aecf4e91025c, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/up-4-mapping-use-cases/SKILL.md
- skills/up-4-mapping-use-cases/references/conventions.md
- skills/up-4-mapping-use-cases/references/goal-levels.md
- skills/up-4-mapping-use-cases/scripts/check_use_case_map.py
- skills/up-4-mapping-use-cases/scripts/spec_model.py
- skills/up-4-mapping-use-cases/templates/use_cases.puml
Every link opens the file at its source, pinned to the revision this page describes.