菜单
Coordinate concurrent agents through collision-safe local claims, bounded leases, idempotent handoffs, and a read-only Mission projection without changing the project or contacting an external service. Use when multiple sessions or worktrees need explicit ownership and handoff evidence.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Configure or explain Recursive Guard, a separately trusted Codex plugin that is inert unless a repository explicitly adds a reviewed .recursive-guard.json policy. Use when a user wants opt-in protection for instruction, provider, hook, or other sensitive repository paths without replacing existing agent configuration.
EXPERIMENTAL. Explore alternative solutions or draft a measurable roadmap as a preview, while preserving existing project instructions and requiring an exact-target approval record before any tracked-file or external action. Use when the user asks to brainstorm, incubate an idea, or preview a roadmap. Do not use it as autonomous build or mutation authority.
Produce a deterministic structural scorecard, run a fixed Atlas-style query, inspect an eval corpus without executing repository code, or emit a review-only proposal diff. Use when a user asks for portable evidence about a repository, its tests or instructions, eval-corpus health, or a proposed verification change without modifying the project.
Capture corrections and follow-ups in private local state, select a compact retrospective, inspect promotion candidates, or emit a review-only learning diff. Use when a user corrects an agent, asks to remember a workflow lesson, requests a retrospective, or wants to improve reusable instructions without silently changing the current repository.
Capture corrections and follow-ups in private local state, select a compact retrospective, inspect promotion candidates, or emit a review-only learning diff. Use when a user corrects an agent, asks to remember a workflow lesson, requests a retrospective, or wants to improve reusable instructions without silently changing the current repository.
Use immediately when no installed skill covers a reusable domain, or when feedback, a mistake, or a better process shows that an existing skill is incomplete or wrong. Record the first observation, create or amend a private candidate, and dogfood it now. Follow provenance to the canonical skill instead of forking it. Recurrence strengthens evidence but never delays a proven correction.
| name | coordinate |
| description | Coordinate concurrent agents through collision-safe local claims, bounded leases, idempotent handoffs, and a read-only Mission projection without changing the project or contacting an external service. Use when multiple sessions or worktrees need explicit ownership and handoff evidence. |
Use the bundled deterministic CLI. Resolve scripts/coordinate.py relative to this file. Existing
project instructions, agents, skills, hooks, provider settings, and repository files remain
authoritative. Coordinate writes only to its user-private state root.
Use a stable operation ID for retry safety and a short owner handle for this work unit:
python3 <skill-dir>/scripts/coordinate.py --repository /path/to/repo \
claim acquire --owner agent-a --target 'src/auth/**' \
--lease-seconds 900 --operation-id task-123-auth --json
A conflict exits with status 3 and reports the current owner, target, claim ID, and expiry. Do not edit the overlapping scope until the claim is released or expired. Renew a live claim before its deadline; release it when work stops. Release and retry operations are idempotent.
Worktrees of one Git repository share a scope derived from Git's common directory. Independent repositories receive different private ledgers. Non-Git directories use their canonical directory identity. Repository paths are hashed before they enter state or output.
python3 <skill-dir>/scripts/coordinate.py --repository /path/to/repo \
handoff send --from agent-a --to reviewer --topic auth \
--message 'PR ready' --ttl-seconds 3600 --operation-id task-123-review --json
python3 <skill-dir>/scripts/coordinate.py --repository /path/to/repo \
handoff inbox --as reviewer --json
Use the same operation ID when retrying a send. Acknowledgement is read-once and idempotent. Messages and identifiers are bounded, sanitized private coordination data—not a transcript store.
python3 <skill-dir>/scripts/coordinate.py --repository /path/to/repo mission view --json
The portable Mission view is a read-only projection over the same claim/handoff ledger. It is not
the full Recursive Mission Control TUI. No remote Agent Mail, Fleet server, MCP adapter, network
connector, or credential flow ships in this beta. integration status reports that local-only
degraded mode without attempting a connection.
Read the state machine, command contract, and security and privacy boundary before sharing a state root or making distributed-consensus claims.