Skip to content

Search skills.../

Agent Skill Search Engine

Search

Search
Categories
Occupations

About

About
Privacy
Terms

© 2026 Skills Pool. All rights reserved.

Role Baton Orchestrator | Skills Pool

Skill File

Role Baton Orchestrator

Orchestrate single-thread baton handoff across Manager -> Collaborator -> Admin -> Consultant with explicit entry/exit contracts.

chf31980 starsApr 14, 2026

Occupation
Categories: Git Workflows

Skill Content

Purpose

Provide deterministic role sequencing for end-to-end tasks while preventing overlap and instruction drift.

Sequence (fixed, per ticket)

Manager
Collaborator
Admin
Consultant

Only one role may be active per ticket at a time. Multiple tickets may have different active roles concurrently.

Parallel dispatch

Manager may hand off N tickets to N different collaborators simultaneously. Each ticket carries its own baton independently. Constraints:

Each collaborator owns exactly one ticket at a time.
Admin merges are serialized (one PR at a time) to avoid conflicts.
Collaborators pull latest main before creating PR.

Research ticket lifecycle

Research tickets skip branch/PR/merge. Baton sequence:

Manager: scope research question, assign collaborator (fleet LLM).

Related Skills

Quick Install

Role Baton Orchestrator

npx skillvault add chf3198/chf3198-devenv-ops-skills-role-baton-orchestrator-skill-md

Download Skill Open repository

Author: chf3198
stars: 0
Updated: Apr 14, 2026
Occupation

On this page

Collaborator: produce research, post findings on ticket.

Admin: review storage placement (wiki/research/), no merge.

Consultant: validate quality, close ticket.

Entry criteria

Manager: task goal known.
Collaborator: manager handoff exists.
Admin: collaborator validation evidence exists.
Consultant: admin execution evidence exists (or explicit N/A).

Stop conditions

Missing required handoff artifact for next role.
Contradictory constraints between role outputs.
Failed mandatory gate without remediation path.

Handoff artifacts

Manager -> Collaborator: scope, constraints, acceptance criteria, gate checklist.
Collaborator -> Admin: changed surfaces + validation evidence.
Admin -> Consultant: operational outcomes + governance/release status.
Consultant -> Finish: risks, confidence, follow-up recommendations.

Required references

repo-standards-router for standards/gates.
workflow-self-anneal only for post-failure/process drift.
Domain skills for specialized checks (release/docs/security/profile).

Consultant rating rubric (quick)

5: contract present but ambiguous; handoffs not reliably testable.
7: clear contracts; occasional ambiguity in escalation boundaries.
9: deterministic handoffs, explicit stop conditions, evidence-complete transitions.
10: same as 9 plus stable multi-session consistency with zero overlap drift.

Output format

ROLE_BATON_REPORT

02

Sequence (fixed, per ticket)

03Parallel dispatch

04Research ticket lifecycle

05Entry criteria

06Stop conditions

07Handoff artifacts

08Required references

09Consultant rating rubric (quick)

10Output format

General and Operations Managers

Openclaw Ghsa Maintainer

Maintainer workflow for OpenClaw GitHub Security Advisories (GHSA). Use when Codex needs to inspect, patch, validate, or publish a repo advisory, verify private-fork state, prepare advisory Markdown or JSON payloads safely, handle GHSA API-specific publish constraints, or confirm advisory publish success.

Gh Issues

Fetch GitHub issues, spawn sub-agents to implement fixes and open PRs, then monitor and address PR review comments. Usage: /gh-issues [owner/repo] [--label bug] [--limit 5] [--milestone v1.0] [--assignee @me] [--fork user/repo] [--watch] [--interval 5] [--reviews-only] [--cron] [--dry-run] [--model glm-5] [--notify-channel -1002381931352]

Security Triage

Triage GitHub security advisories for OpenClaw with high-confidence close/keep decisions, exact tag and commit verification, trust-model checks, optional hardening notes, and a final reply ready to post and copy to clipboard.

Github

GitHub operations via `gh` CLI: issues, PRs, CI runs, code review, API queries. Use when: (1) checking PR status or CI, (2) creating/commenting on issues, (3) listing/filtering PRs or issues, (4) viewing run logs. NOT for: complex web UI interactions requiring manual browser flows (use browser tooling when available), bulk operations across many repos (script with gh api), or when gh auth is not configured.

Author Contributions

Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

microsoft184.0k

Repository Setup

Initialize a worktree-based repo layout for parallel development. Creates a main worktree, a reviews worktree for PR reviews, and N numbered work branches. Handles .env creation, dependency installation, and branchlet config. TRIGGER when user asks to set up the repo from scratch, initialize worktrees, bootstrap their dev environment, "setup repo", "setup worktrees", "initialize dev environment", "set up branches", or when a freshly cloned repo has no sibling worktrees.

Significant-Gravitas183.5k

General and Operations Managers