ai/gemini-content-team/skills/cco-orchestration/SKILL.md
Executable checklist for one cco pipeline run (parallel groups, METRICS_READ, audit NDJSON, n8n gates).
npx skillsauth add akshay-na/dotfiles cco-orchestrationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Read rules/orchestration.md, rules/repo-hygiene.md, rules/project-identity.md, skills/project-identity/SKILL.md, rules/brain-paths.md, rules/brain-conventions.md, and rules/cco-single-invocation.md first.
<content-brain> per rules/project-identity.md (same ~/ai-brain/projects/<project_name>/ as Cursor kb-identity).run_id, action, event_id idempotency.git pull for active workspace per rules/repo-hygiene.md when using git-tracked brain or project files.<content-brain>/analytics/metrics-current.json, metrics-latest.md; append metrics_snapshot_read to ~/.gemini/memory/observability/events.jsonl.~/.gemini/memory/pipelines/current-state.md); align FSM with action.phase_enter audit for current phase.ultra except security-autoclarity.handoff audit (hashes not bodies).phase_exit audit.cco again or to “start BRIEF” manually. After RESEARCH, enter BRIEF (cmo, vp-brand, vp-editorial per orchestration) in the same invocation / continued session until awaiting_user.awaiting_user; emit cco.run.awaiting_user with CcoRunReport JSON only.continue: METRICS*READ if policy says so; archivist when publish metadata present; phase*\* audits.revise: jump to last_checkpoint from run record; re-run downstream; emit cco.run.revision_applied when done.cco.run.completed, ledger consistent under <content-brain>/_meta/; commit via normal git if applicable.~/.gemini/memory/pipelines/failures/<run_id>-<ts>.md, cco.run.failed, FSM failed.Third production external agent; caveman in outbound JSON; skipping QA before awaiting_user.
development
Discovery + naming convention reference for typed dev/SME/QA/devops team members in any workspace folder. Primary consumer: `tech-lead` (org-tier).
devops
Automated task classification, agent selection, and state tracking. Use when routing tasks to agents, selecting pipelines, or managing task state.
testing
Use when designing scalable systems, evaluating consistency models, planning state management, making architectural decisions, or when trade-offs around coupling, failure isolation, and reversibility need explicit reasoning before implementation.
tools
CTO/tech-lead helper — split work into disjoint shard briefs with caps (instance_cap, partition_basis, determinism keys).