manager-ticket-lifecycle

Orchestrate GitHub issue handoffs across Manager, Collaborator, Admin, and Consultant roles.

Updated Apr 11, 2026

Search Tags:#workflow #github #agile #lifecycle #ticket #baton

Ready to run

npx skills add https://github.com/chf3198/devenv-ops --skill manager-ticket-lifecycle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: manager-ticket-lifecycle
Source: https://github.com/chf3198/devenv-ops/tree/main/skills/manager-ticket-lifecycle
Command: npx skills add https://github.com/chf3198/devenv-ops --skill manager-ticket-lifecycle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Orchestrates cross-role work by treating GitHub issues as the baton that moves from Manager to Collaborator to Admin to Consultant.

Core Features & Use Cases

Establishes a structured lifecycle where a single issue acts as a handoff baton across roles.
Enforces a label-based workflow (type, status, priority, area, role) and supports epic/story/task/bug types.
Enables consistent governance, auditability, and handoff visibility across teams.

Quick Start

Create a GitHub issue and apply the initial baton labels to start the lifecycle.

Frequently Asked Questions about manager-ticket-lifecycle

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

FAQPage Schema

How do I manage a GitHub issue lifecycle across multiple roles?▼

A GitHub issue lifecycle across multiple roles is managed by treating the issue as a baton passed from Manager to Collaborator, Admin, and Consultant using a structured label taxonomy for type, status, priority, area, and role.

What is a baton-driven workflow for GitHub issues?▼

A baton-driven workflow uses a single GitHub issue as a handoff token across team roles. It enforces structured transitions and role-specific comments to ensure consistent governance and auditability.

How do I set up a GitHub issue workflow with label-based governance?▼

Set up GitHub issue governance by applying a formal label taxonomy covering type, status, priority, area, and role to guide ticket creation, decomposition, and closure across epic, story, task, and bug types.

Can I use GitHub issues for agile cross-role ticket handoffs?▼

Yes, GitHub issues support agile cross-role ticket handoffs by applying initial baton labels that move the issue from managers who create them to collaborators, admins, and consultants who validate.

What is the best way to track status transitions for GitHub issue types?▼

Track status transitions for GitHub issue types by enforcing a label-based workflow that defines a clear status flow for epics, stories, tasks, and bugs during ticket decomposition and closure.