Skip to content
v1.8.2MIT

Stack-neutral skills for a specification-first workflow with use cases: requirements, entity model, use case specifications, review, implementation, tests, change handling, coverage audit, recovery of existing systems and scaling to several teams.

up-4-mapping-use-cases

Finds the use cases a system needs and records them as the use case overview (docs/use_cases.md: a scope list and delivery order written by people, and an actor-goal table and Mermaid diagram generated from the use case files), creating a stub for each mapped use case. Tests user-goal level, aggregates or splits Manage-X goals, moves multi-role or waiting flows to BPMN, and checks functional requirement coverage. Use when the user asks which use cases exist or are missing, whether a goal is a use case, for a diagram or actor-goal list, to split or merge use cases, to decide scope, or to check requirement coverage. Not for writing one use case's steps, bounded contexts or draw.io.

Read SKILL.md at the source

Pinned to revision a5e959f4838b, so it is the text this page describes rather than whatever the author pushed since.

Files

Every link opens the file at its source, pinned to the revision this page describes.