spawning-a-role

Generate validated Claude Code spawn commands from role templates and orchestration config.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/tuvens/phased-development --skill spawning-a-role
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: spawning-a-role
Source: https://github.com/tuvens/phased-development/tree/main/skills/spawning-a-role
Command: npx skills add https://github.com/tuvens/phased-development --skill spawning-a-role

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the friction and mistakes involved in starting a Claude Code role session from a phased-development project, especially when the role must match a template, alias, and session-name convention.

Core Features & Use Cases

  • Template Resolution: Finds the correct lead or internal role template, including alias-backed role names that map to a canonical agent.
  • Config-Aware Spawning: Reads project orchestration settings and substitutes the correct project name, branch, repository, and root path values.
  • Validation Guardrails: Checks session-name shape before spawning so lead, phase, epic, and sprint sessions stay routable and consistent.
  • Use Case: A project orchestrator can quickly generate a valid spawn command for a VP, tech lead, or sprint lead without hand-editing prompt bodies or risking a malformed session name.

Quick Start

Use the spawning-a-role skill to read the project orchestration config, resolve the requested role template, and produce a ready-to-run Claude Code spawn command.

Frequently Asked Questions about spawning-a-role

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

FAQPage Schema
How do I generate a Claude Code spawn command for a specific role template?

Claude Code role spawning requires reading orchestration config values, resolving canonical lead or internal templates, substituting placeholders, and enforcing a remote-control session-name pattern before producing a valid spawn command.

What is template alias resolution in GitHub-based orchestration workflows?

Template alias resolution maps an alias-backed role name to a canonical agent template, ensuring the correct GitHub-based Claude Code role is dispatched without manually searching for the underlying template file.

How do I validate session naming conventions for phased-development projects?

You validate session naming conventions by enforcing the remote-control session-name pattern before spawning, ensuring lead, phase, epic, and sprint sessions remain routable and consistent across phased-development workflows.

Can I use orchestration config values to bootstrap a project and dispatch a lead role?

Yes, config-aware spawning reads project orchestration settings to substitute the correct project name, branch, repository, and root path values, covering both project bootstrap and lead-role dispatch for GitHub-based projects.

Why does my role spawn command fail with a malformed session name?

Role spawn commands fail when the session name does not match the required remote-control session-name pattern, triggering validation guardrails that prevent inconsistent or unroutable lead, phase, epic, and sprint sessions.