promote

Promote tasks and phases from an orchestrator's staging area to a sub-repo's task system.

Updated May 7, 2026
One-click install
npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill promote-chazzcoin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: promote
Source: https://github.com/ChazzCoin/claude-orchestrator/tree/main/kit/skills/promote
Command: npx skills add https://github.com/ChazzCoin/claude-orchestrator --skill promote-chazzcoin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the process of promoting tasks or phases from the orchestrator's staging area to a target sub-repo's task system, reducing manual overhead and ensuring consistency across the development workflow.

Core Features & Use Cases

  • Task Promotion: Move proposed tasks from the orchestrator's staging area to a sub-repo's task system.
  • Phase Promotion: Promote entire phases along with their associated tasks.
  • Validation: Ensures that tasks meet the required specifications before promotion.
  • PR Creation: Automatically creates pull requests for tasks in the sub-repo.
  • Archiving: Moves promoted proposals to an archive for future reference.

Quick Start

To promote a task, use the command: /promote <slug>. To promote a phase, use: /promote phase <id> in <repo>.

Frequently Asked Questions about promote

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

FAQPage Schema
How do I promote tasks from an orchestrator staging area to a sub-repo task system?

To promote tasks from an orchestrator staging area to a sub-repo task system, use the `/promote <slug>` command. This automates moving proposed tasks, validates specifications, creates pull requests, and archives promoted proposals automatically.

Can I promote an entire phase of tasks to a sub-repo at once?

You can promote an entire phase of tasks to a sub-repo by using the `/promote phase <id> in <repo>` command. This moves the phase and its associated tasks from the orchestrator staging area into the target sub-repo's task system.

What is needed to automate pull request creation for task promotion?

Automating pull request creation for task promotion requires a cloned sub-repo and a valid proposal in the orchestrator's backlog. The process also requires strict adherence to governance rules and task specification validation before creating PRs.

How does task specification validation work during phase promotion?

Task specification validation during phase promotion ensures tasks meet required specifications before moving to the sub-repo. This governance check prevents invalid proposals from advancing from the orchestrator's staging area into the target task system.

Why does task promotion fail when moving proposals to a sub-repo?

Task promotion to a sub-repo fails if the sub-repo is not cloned, the orchestrator backlog lacks a valid proposal, or governance rules and task specification validation are not met. Ensure all prerequisites are satisfied before executing promotion commands.