uml-diagramslisted

# Requirements-Spec UML Diagrams Create or review requirements-specification UML diagrams. The target project's diagram profile, terminology, document structure and source/render ownership are authoritative. Use the neutral rules here only where the project is silent. Prefer PlantUML source (`.puml`) and inspect a render before finalising. ## Platform choice 1. PlantUML first when the project has no established diagram tool: use cases, packages, actors, include/extend, swimlanes, decisions, forks, joins, and finals auto-route reliably. 2. Preserve an established project tool. For manual SVG/Python, read `references/manual-rendering-quality.md`. 3. Otherwise use Excalidraw or D2 only when explicitly requested; route D2 to `d2-diagrams`. ## Workflow 1. Read the relevant guide: - package overview or per-package use case diagram: `references/use-case-and-package-rules.md` - activity diagram: `references/activity-rules.md` - before finalising: `references/common-mistakes.md` - high-stakes deliverable: `references/multi-agent-review-loop.md` 2. If no project template exists, start from the matching skill template: - `templates/use_case_package_template.puml` - `templates/use_case_diagram_template.puml` - `templates/activity_diagram_template.puml` 3. Use stable aliases consistent with the project. 4. Lint with the skill-relative script (the linter is heuristic, not a project conformance oracle): ```bash python3 "${AGENTS_HOME:-$HOME/.ag