conductor-upgrade-version

Coordinate multi-version upgrades by sequencing feature development before bug fixing.

3|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/rashidee/co2-skills --skill conductor-upgrade-version
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: conductor-upgrade-version
Source: https://github.com/rashidee/co2-skills/tree/main/skills/conductor-upgrade-version
Command: npx skills add https://github.com/rashidee/co2-skills --skill conductor-upgrade-version

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates end-to-end version upgrades by coordinating feature development and bug fixing in a strict, version-by-version flow, ensuring code exists before bugs are reproduced and fixed.

Core Features & Use Cases

  • Coordinated Phase A (Feature Development) and Phase B (Bug Fixing) per version to deliver stable upgrades.
  • Sequential version processing with automatic progression through UPGRADE_MASTER.md tracking and Ralph Loop integration.
  • Auto-resumption after interruptions using the centralized tracking file and single Ralph Loop session.

Quick Start

Start the upgrade by specifying the target application and optional version list to begin Phase A for the first version.

Frequently Asked Questions about conductor-upgrade-version

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

FAQPage Schema
How do I orchestrate multi-version upgrades while coordinating feature development and bug fixing?▼

You orchestrate multi-version upgrades by pairing feature development and bug fixing in a controlled, version-by-version flow. Phase A handles features and Phase B handles bugs, ensuring code exists before bugs are reproduced and fixed.

How does version upgrade orchestration handle interruptions during sequential version processing?▼

Version upgrade orchestration handles interruptions by using a centralized UPGRADE_MASTER.md tracking file. This file enables auto-resumption of the upgrade process, allowing the workflow to pick up exactly where it left off.

What is the best way to enforce strict version sequencing during an end-to-end software upgrade?▼

The best way to enforce strict version sequencing is through an orchestrated workflow that processes ordered versions sequentially. It ensures Phase A completes before Phase B for each version, integrating progress tracking and artifact checks.

Do I need a specific tracking file to resume version upgrades after a failure?▼

Yes, you need the UPGRADE_MASTER.md file to resume version upgrades after a failure. It serves as the centralized tracking mechanism that records progress and enables auto-resumption within a single Ralph Loop session.

Can I run feature development and bug fixing phases at the same time for a version upgrade?▼

No, you cannot run feature development and bug fixing phases simultaneously for the same version. The orchestration enforces strict sequencing, requiring Phase A features to fully complete before Phase B bug fixing begins.

Why does my version upgrade workflow require bug fixing to happen after feature development?▼

Your version upgrade workflow requires bug fixing after feature development to ensure the code exists before bugs are reproduced and fixed. This controlled Phase A and Phase B sequencing delivers stable upgrades across ordered versions.