Menu
Orchestrate multi-sprint phase execution as team-lead. Manages sprint waves, scrum-master lifecycle, PR merges, cwy reviews, and integration branch strategy. This skill is for team-lead only, not for scrum-masters.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Reusable QA orchestration skill for GitHub PRs. Use for multi-pass QA, CI monitoring, and template-driven findings and final quality reports.
Orchestrate Wyvern sprint/phase work inside a single Cursor session. Parent spawns reviewers and rust-developer; Task(cursor-quality-mgr) enforces spawn proof, aggregates fenced JSON evidence, triages findings, publishes PR reports, and owns the QA gate. Use when the user asks for /cursor-orchestration, Cursor-session phase/sprint orchestration, or same-session QA via cursor-quality-mgr. Never use ATM quality-mgr or codex-orchestration while this skill governs the session.
Orchestrate sprint work where team-lead coordinates, cwy is the sole developer, and quality-mgr enforces the QA gate.
Orchestrate pre-dispatch QA finding triage as team-lead. Launch one qa-triage agent per finding, collect phase-scoped Turtle records, aggregate by promoted branch, and only then dispatch branch-scoped fix assignments to arch-ctm.
Team-lead drives plan hardening after the current plan state already exists in repo docs.
Repair Claude teammate routing after same-session compaction or resume when wyvern still exists on disk and the saved leadSessionId still matches the current SESSION_ID, but SendMessage or teammate reachability is broken.
| name | phase-orchestration |
| version | 0.1.0 |
| description | Orchestrate multi-sprint phase execution as team-lead. Manages sprint waves, scrum-master lifecycle, PR merges, cwy 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.cwy 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:
cwy 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 cwy
review via ATM CLI. Do not block the next eligible sprint unless cwy
reports critical blocking findings.
If cwy 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 cwy:
atm send cwy "message"
atm read
atm inbox
Use tmux nudges when required by the local runtime setup.
rust-developer as the scrum-master subagent type