Menu
Orchestrate multi-sprint phase execution as team-lead. Manages sprint waves, scrum-master lifecycle, PR merges, arch-ctm reviews, and integration branch strategy. This skill is for team-lead only, not for scrum-masters.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Team-lead drives plan hardening after the current plan state already exists in repo docs.
Repair ATM teammate coordination after same-session compaction or resume when atm-dev still exists on disk and the saved leadSessionId still matches the current SESSION_ID, but named-teammate ATM reachability is broken.
Session initialization for the team-lead identity. Confirms identity and detects whether a full team restore is needed. Only run when ATM_IDENTITY=team-lead.
Run or inspect the Phase Z smoke harness for atm-core. Use when implementing or operating `just smoke`, `just smoke fast`, or `just smoke thorough`, when rendering `reports/smoke/*`, when checking the frozen Phase Z row map, or when triaging smoke findings against retained logs and report artifacts.
Create, manage, scan, update, and clean up git worktrees for parallel development with protected branch safeguards. Use when working on multiple branches simultaneously, isolating experiments, updating protected branches (main/develop), or when user mentions "worktree", "parallel branches", "feature isolation", "branch cleanup", "worktree status", or "update main/develop".
Orchestrate atm-core sprint work where team-lead coordinates, arch-ctm is the sole developer, and quality-mgr enforces the QA gate.
| name | phase-orchestration |
| version | 0.1.0 |
| description | Orchestrate multi-sprint phase execution as team-lead. Manages sprint waves, scrum-master lifecycle, PR merges, arch-ctm reviews, and integration branch strategy. This skill is for team-lead only, not for scrum-masters. |
| depends_on | {"scrum-master":"0.x","rust-developer":"0.x","rust-qa-agent":"0.x","req-qa":"0.x","rust-architect":"0.x"} |
This skill defines how team-lead orchestrates a development phase consisting of multiple sprints with dependency-aware parallelism.
Audience: team-lead only. Scrum-masters have their own process defined in
.claude/agents/scrum-master.md.
Before starting a phase:
docs/project-plan.md or a linked phase document.integrate/phase-{N} exists and is up to date with
develop.arch-ctm is running and reachable via ATM CLI.Read the phase plan and identify:
For each sprint, respecting dependency order:
Each sprint gets a fresh scrum-master. Do not reuse scrum-masters across sprints.
{
"subagent_type": "scrum-master",
"name": "sm-{phase}-{sprint}",
"team_name": "<team-name>",
"model": "sonnet",
"prompt": "<sprint prompt>"
}
Critical rules:
subagent_type must be scrum-mastername is requiredteam_name is requiredThe sprint prompt should include:
rust-architectAfter each scrum-master reports completion:
arch-ctm to run a self-directed Rust best-practices
sweep on the integration branch using the planned QA-1 review targets and
fix all findings found thereintegrate/phase-{N} in dependency orderAfter every sprint PR is merged to integrate/phase-{N}, request an arch-ctm
review via ATM CLI. Do not block the next eligible sprint unless arch-ctm
reports critical blocking findings.
If arch-ctm finds issues:
integrate/phase-{N}rust-qa-agent and req-qa before mergeBefore starting the next wave:
After all sprints merge:
integrate/phase-{N} -> developUse ATM CLI for arch-ctm:
atm send arch-ctm "message"
atm read
atm inbox
Use tmux nudges when required by the local runtime setup.
rust-developer as the scrum-master subagent type