What problem does it solve? Closing a RUP project requires coordinating production deployment, user acceptance testing, defect triage, training, and formal sign-off, and teams often skip steps or declare release prematurely. This Skill structures the entire Transition phase so the Product Release (PD) milestone is reached with documented evidence. ## Core Features & Use Cases - Deployment and UAT orchestration: Produces deployment plans, rollback plans, UAT scenarios per critical use case, and a severity-classified defect log (Severity 1-4) with prioritization rules. - PD milestone evaluation: Applies explicit go/no-go criteria (production live, Severity 1 = 0, Product Acceptance Sign-off, training complete, documentation delivered) to decide between closing the project or running another Transition iteration. - Kaupamex artifact mapping: Maps every RUP deliverable onto docs/source/ .rst initiative files (tareas, progreso, lecciones-aprendidas) instead of standalone markdown reports. - Use Case: After Construction reaches IOC, use this Skill to plan the beta release, run UAT with real users, triage reported defects, complete training, and record the formal Product Acceptance Sign-off in the initiative's progress file. ## Quick Start Run the rup-transition skill to plan the production deployment and UAT for the active initiative and evaluate whether the PD milestone criteria are met.
