Menu
Orchestrate multi-sprint phases where csc (Codex) is the sole developer, with pipelined QA via quality-mgr teammate. Team-lead tracks findings and schedules fix passes.
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
Thin Claude skill wrapper for Synaptic Canvas package management through `sc --json`.
Team-lead delegates plan hardening to csc after the user has already discussed the plan details with csc.
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".
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.
| name | codex-orchestration |
| description | Orchestrate multi-sprint phases where csc (Codex) is the sole developer, with pipelined QA via quality-mgr teammate. Team-lead tracks findings and schedules fix passes. |
This skill defines how the team-lead (ARCH-ATM) orchestrates phases where csc (Codex) is the sole developer, executing sprints sequentially while QA runs in parallel via a dedicated quality-mgr teammate.
Audience: Team-lead only.
When to use: When a phase's implementation is done entirely by csc (a Codex agent communicating via ATM CLI), not by Claude Code scrum-masters. This pattern was proven in Phase M (8 sprints) and Phase O.
Before starting a phase:
integrate/phase-{P} created off develop$ATM_TEAM) is active with team-lead and csc as membersatm send csc "ping")team-lead (ARCH-ATM)
├── csc (Codex) ──── sole developer, sequential sprints
│ communicates via ATM CLI only
└── quality-mgr (Claude Code) ──── QA coordinator teammate
spawns go-qa-agent + req-qa-agent + arch-qa-agent as background agents
Key principle: csc does NOT wait for QA. He proceeds to the next sprint as soon as he completes one, unless there are outstanding fix requests from earlier sprints.
git fetch origin develop
git branch integrate/phase-{P} origin/develop
git push -u origin integrate/phase-{P}
# Use sc-git-worktree skill
/sc-git-worktree --create feature/p{P}-s1-{slug} integrate/phase-{P}
Spawn once per phase. The quality-mgr persists across all sprints.
Use the Task tool with name parameter to spawn as a named teammate:
{
"subagent_type": "quality-mgr",
"name": "quality-mgr",
"team_name": "$ATM_TEAM",
"model": "sonnet",
"prompt": "You are quality-mgr for Phase {P}. You will receive QA assignments from team-lead for each sprint as they complete. Stand by for first assignment. Integration branch: integrate/phase-{P}. Phase docs: docs/project-plan.md, docs/requirements.md."
}
atm send csc "Phase {P} Sprint {P}.1 assignment: {title}
Worktree: /path/to/worktree
Branch: feature/p{P}-s1-{slug}
PR target: integrate/phase-{P}
Deliverables:
- {list deliverables}
Requirements: docs/requirements.md ({relevant FRs})
Sprint plan: docs/project-plan.md (Phase {P} section)
When complete: commit, push, then notify me via atm send with branch + commit SHA. Do not create PR."
Timeline:
csc: [── S.1 ──]──fixes──[── S.2 ──]──fixes──[── S.3 ──]
quality-mgr: [── QA S.1 ──] [── QA S.2 ──] [── QA S.3 ──]
team-lead: assign S.1 → track → assign S.2 → track → assign S.3 → track
integrate/phase-{P} and immediately starts CI monitoring:
atm gh monitor pr <PR_NUMBER>
/sc-git-worktree --create feature/p{P}-s{N+1}-{slug} feature/p{P}-s{N}-{slug}
"Run QA on Sprint {P}.{S}. Worktree: {path}. Sprint deliverables: {summary}.
Design docs: {list}. PR: #{N}."
Priority order for csc:
Fix workflow:
# csc fixes on the sprint's original worktree
# csc pushes fix commits to same PR branch
# team-lead asks quality-mgr to re-run QA on the fixed worktree
# If QA passes, team-lead merges PR to integration branch
After fixes merge to integrate/phase-{P}:
git fetch origin
git merge origin/integrate/phase-{P}
Assignment format:
Run QA on Sprint {P}.{S}: {title}
Worktree: {absolute path}
Sprint deliverables: {bullet list}
Design docs: {list of relevant doc paths}
PR: #{number}
Re-run after fixes:
Re-run QA on Sprint {P}.{S} (post-fix).
Worktree: {path}
Fixed findings: {list of QA IDs addressed}
quality-mgr reports PASS/FAIL with finding IDs. Team-lead tracks:
| Sprint | QA Run | Verdict | Blocking Findings | Status |
|---|---|---|---|---|
| O.1 | 1 | FAIL | QA-001, QA-002 | Fixes assigned |
| O.1 | 2 | PASS | — | Merged |
| O.2 | 1 | PASS | — | Merged |
OPEN → assigned to csc → FIXED (csc pushes) → re-QA → VERIFIED (QA passes)
→ WONTFIX (team-lead approves deviation)
integrate/phase-{P} (never develop directly)integrate/phase-{P} → developAll csc communication is via ATM CLI. Follow the dogfooding protocol (ACK → work → complete → ACK).
atm send csc "message"
atm read
Use ATM first:
atm send csc "You have unread ATM messages. Run: atm read --team $ATM_TEAM"
If your local runtime uses tmux pane orchestration, tmux nudges are optional and environment-specific.
When csc is waiting for assignments, tell him:
"Standing by? Use: atm read --team $ATM_TEAM --timeout 60"
This keeps him responsive without busy-polling.
After all sprints pass QA and merge to integration branch:
integrate/phase-{P} → developdevelop — chain from previous sprint or integration branch