role-registry

Name: role-registry
Availability: InStock
Author: tuvens

Resolve role aliases and reporting hierarchies for phased software project coordination.

Updated Aug 27, 2026

Search Tags:#agent coordination #workflow routing #session orchestration #role management #signaling protocol #bootstrap contracts

Ready to run

npx skills add https://github.com/tuvens/phased-development --skill role-registry

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: role-registry
Source: https://github.com/tuvens/phased-development/tree/main/skills/role-registry
Command: npx skills add https://github.com/tuvens/phased-development --skill role-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines how phased-development agents identify one another, route work, and keep long-running multi-session projects moving without confusion or idle time.

Core Features & Use Cases

Role Alias Resolution: Maps informal titles like PM, CTO, or Sprint Lead to canonical roles and session names.
Hierarchy and Signaling Rules: Clarifies who reports to whom, when to signal upward or downward, and which communication channel each tier must use.
No-Idleness Doctrine: Reinforces continuous progress, escalation, and acknowledgment loops for orchestration sessions.
Use Case: Use this Skill when launching or coordinating leadership, phase, epic, sprint, or QA roles in a multi-phase software program.

Quick Start

Ask the skill to map the project roles, reporting chain, and signaling obligations for your phased-development workspace.

Frequently Asked Questions about role-registry

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

FAQPage Schema

How do I coordinate agent roles and reporting hierarchies for a multi-phase software project?▼

Agent role coordination uses canonical role resolution to map informal titles like PM or CTO to session names, clarifies reporting chains, and enforces tier-aware communication rules for phased software project orchestration.

What is session signaling protocol and how does it prevent idle time in multi-agent orchestration?▼

Session signaling protocol defines upward and downward communication obligations across tiers, enforcing a no-idleness doctrine that requires continuous progress, escalation, and acknowledgment loops for long-running orchestration sessions.

How do I set up workflow routing and role contracts for leadership-team orchestration?▼

Workflow routing setup requires bootstrap-first role contracts that define canonical roles, establish phase and epic dispatch rules, and map sprint-agent delegation paths before leadership-team orchestration sessions begin.

Can I map informal project titles to canonical roles for sprint-agent delegation?▼

Role alias resolution maps informal titles like Sprint Lead or CTO to canonical roles and session names, enabling accurate sprint-agent delegation and tier-aware communication across phased-development workspaces.

When do I need bootstrap contracts for phase and epic dispatch in multi-session projects?▼

Bootstrap contracts are needed when launching or coordinating leadership, phase, epic, sprint, or QA roles in a multi-phase software program to ensure canonical role resolution and enforce no-idleness from the start.