Menu
Initialize and manage Transition phase activities - deploy to users
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
One-command project setup for OpenUP - interactive initialization wizard
Mark a task as complete, update roadmap, commit changes, and prepare traceability logs
Execute an already-claimed lane's Operations boxes with script/judgment classification — script steps run directly with zero self-brief, judgment steps self-brief and execute. Handles only pick/resume; every other resolve path routes to /openup-next.
Run OpenUP Assess Results at iteration end — check evaluation criteria, demo only completed acceptance-tested work, feed discovered work back, and trigger the milestone review at a phase boundary
Run the phase milestone go/no-go — prepare derived evidence, pause for the human decision via an input-request, and record the milestone (never advance the phase itself)
Begin a new OpenUP iteration with proper phase context and task selection
| name | openup-transition |
| description | Initialize and manage Transition phase activities - deploy to users |
| model | haiku |
| arguments | [{"name":"activity","description":"Specific activity to perform (initiate, check-status, next-steps)","required":false}] |
This skill guides you through the Transition phase of OpenUP - deploying to users.
Thin front over the process map (T-077). This phase's activity composition is data, not prose: run
python3 scripts/openup-process-map.py activities-for transitionfor the authoritative ordered activities (each resolved to its role + skills), and let/openup-start-iterationPlan Iteration generate this phase's work-item lanes from that map. The guidance below is human-facing reference — the map + Plan Iteration are the source of truth for what a Transition iteration runs.
Use this skill when:
Do NOT use this skill when:
/openup-construction)After using this skill, verify:
Goal: Deploy the system to users and ensure user satisfaction Duration: Typically 2-4 weeks Key Milestone: Product Release
If docs/project-config.yaml defines an ordered environments: list (see
docs-eng-process/project-config.md), Transition walks that chain hop by
hop instead of a single hop to production:
name and (except the last) a promotion: criterion — a
free-text, checkable statement of what must be true before the release moves
to the next environment.initiate): the hop's promotion: criterion + the relevant
completion criteria above.beta entry — rather than being an unanchored
activity. Per-environment flag default states come from each task's
## Rollout section.check-status reports which environment the release currently sits in
and which promotion criteria block the next hop.If the key is absent, skip this step — single-hop deployment to production, unchanged framework default.
Read docs/project-status.md to:
transitioninitiate: Start Transition phase
docs/project-status.md to set phase: transitionenvironments: chain when configured (step 0), single-hop otherwisedocs/roadmap.md with transition taskscheck-status: Review progress
next-steps: Get recommendations
For Transition phase work, create a team with:
Final Testing - Comprehensive testing including:
Deployment Preparation - Prepare for release:
User Preparation - Prepare users:
Release - Deploy to production:
docs-eng-process/openup-knowledge-base/practice-management/risk_value_lifecycle/guidances/concepts/phase-transition.mddocs-eng-process/openup-knowledge-base/core/role/roles/tester-5.mddocs-eng-process/openup-knowledge-base/core/role/roles/project-manager-4.md