What problem does it solve? Keeping UML diagrams, use case specifications, code, and the formal delivery document consistent is error-prone when done ad hoc. This Skill centralizes the rules for which artifacts each TP requirement demands, where they live under diagramas/<requisito>/, how they are named, and how they stay balanced with the real code and SQL Server database. ## Core Features & Use Cases - Requirement catalog enforcement: Defines exactly which artifacts each requirement (T0X technical, G0X integration, N0X business) needs, including general diagrams (classes, DER, sequence, components, navigation) and per-use-case sequence diagrams. - Sub-skill orchestration: Delegates .puml creation to the PlantUML sub-skill and use case specification generation (one JSON per requirement, plus .docx/.md outputs and a consolidated document) to the tp-use-case-spec sub-skill. - Database-grounded DERs: DERs are built by inspecting the real SQL Server database (TpCatedraIDS) via sqlcmd queries, cross-checked against script_bd.sql. - Use Case: After finishing the T05 multidioma requirement, ask the Skill to generate its class diagram, DER from the live database, one sequence diagram per use case, and the T05-multidioma-casos-de-uso.json specification, then validate everything against the checklist. ## Quick Start Use the tp-uml-y-casos-de-uso skill to create the diagrams and use case specifications for requirement T02 login-logout now that its development is complete.
