rup-transition

Executes the RUP Transition phase covering production deployment, UAT, defect resolution, and PD milestone closure.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/jcg-admin/IACT-ui --skill rup-transition-jcg-admin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rup-transition
Source: https://github.com/jcg-admin/IACT-ui/tree/main/.claude/skills/rup-transition
Command: npx skills add https://github.com/jcg-admin/IACT-ui --skill rup-transition-jcg-admin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Managing the final phase of a RUP project—deploying to production, running user acceptance testing, triaging post-beta defects, and obtaining formal product acceptance—is complex and error-prone without a structured process. This Skill guides teams through the RUP Transition phase to reach the PD (Product Release) milestone with clear criteria and artifacts. ## Core Features & Use Cases - Deployment Planning: Structures deployment plans, release notes, rollback plans, and communication plans before going live. - UAT & Defect Management: Provides severity classification (Severity 1-4), prioritization rules, and UAT execution guidance with real users. - PD Milestone Evaluation: Defines explicit go/no-go criteria including Severity 1 = 0, Product Acceptance Sign-off, training completion, and documentation delivery. - Use Case: A team that finished Construction with IOC reached uses this Skill to plan the beta release, run UAT with real users, triage reported defects, deliver training, and produce the formal Product Acceptance Sign-off document. ## Quick Start Ask the AI to run the RUP Transition phase for your project and generate the transition report with deployment plan, UAT results, defect log, and PD milestone evaluation.

Frequently Asked Questions about rup-transition

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run the RUP Transition phase for a software project?▼

Start after reaching the IOC milestone in Construction. Prepare a deployment plan with rollback procedures, run UAT with real end users, classify defects by severity, deliver training, and evaluate the PD milestone criteria before formal project closure.

What are the criteria for the PD Product Release milestone in RUP?▼

PD requires the system deployed in production, zero Severity 1 defects, a formal Product Acceptance Sign-off from the sponsor, completed training for all audiences, and delivered documentation. All five criteria must be met to close the project.

How are defects prioritized during user acceptance testing?▼

Defects are classified into four severity levels from Critical to Cosmetic. Within Severity 1 and 2, prioritize by frequency of impact and whether the defect blocks a Must Have use case. All Severity 1 defects must be fixed before Severity 2 work begins.

When should I not start the RUP Transition phase?▼

Do not start Transition without the IOC milestone reached, since deploying with open critical defects damages user adoption. Also skip it if the system is already accepted in production, meaning PD was already achieved.

How long should the RUP Transition phase take?▼

Transition should last 1-2 weeks for small projects, 2-4 weeks for medium ones, and 4-8 weeks for large ones. It should not exceed 20 percent of total project effort; exceeding that signals Construction was incomplete.