Menu
Orchestrate phased work where cobs is the sole developer and quality-mgr enforces the QA gate for sc-observability.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use when the user says things like "bring sc-observability into an existing Rust project" or "adopt sc-observability in a codebase that already has logging". Adopts sc-observability incrementally with a logging-first path and focused migration references for log, tracing, or custom JSONL setups.
Use when the user says things like "set up sc-observability in a new Rust project" or "add structured logging to a new Rust app". Bootstraps a new project with sc-observability from crates.io using the shared light-logging house style, ~/.<app> log roots, and a rendered starter template.
Use when the user says things like "review this project for sc-observability best practices" or "check whether our logging setup matches the sc-observability standard". Reviews a Rust project's observability setup against the shared house style and recommends missing baseline items and easy improvements.
Orchestrate multi-sprint phase execution as team-lead (ARCH-ATM). Manages sprint waves, scrum-master lifecycle, PR merges, cobs reviews, and integration branch strategy. This skill is for the TEAM-LEAD only, not for scrum-masters.
Reusable QA orchestration skill for GitHub PRs. Use for multi-pass QA, CI monitoring with `atm gh monitor`, one-shot PR reporting with `atm gh pr report`, and template-driven findings/final quality reports.
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 phased work where cobs is the sole developer and quality-mgr enforces the QA gate for sc-observability. |
This skill defines a lightweight phase workflow for standalone repos like
sc-observability.
team-lead coordinatescobs is the sole developerquality-mgr runs QA after each sprint deliveryThe repo may use either:
main, orintegrate/phase-{P} branch when a phase needs a staging branchUse the pr_target in the assignment as the source of truth.
Before starting:
docs/requirements.md, docs/architecture.md, and docs/project-plan.md
describe the sprint.main or integrate/phase-{P}).quality-mgr, rust-qa-agent, req-qa, and arch-qa are available.cobs using dev-template.xml.j2.cobs ACKs, implements, commits, pushes, and reports the branch + SHA.quality-mgr using qa-template.xml.j2.quality-mgr runs:
rust-qa-agentreq-qaarch-qacobs.Use standard GitHub CLI for PR checks:
gh pr checks <PR> --watchgh pr view <PR> --json mergeStateStatus,reviewDecisionDo not assume ATM-specific PR monitoring commands exist in this repo.
Create sprint worktrees with normal git worktree commands when needed:
git worktree add ../<repo>-worktrees/<branch-name> -b <branch-name> <base-branch>
Every ATM task message must follow: