メニュー
Use when the user invokes `$team-progress`, asks to sync recent progress from other team members, or asks who has blockers or PR/MR items needing review in a team-collab project.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when the current repo is explicitly governed by team-collab: `obsidian-docs/` exists in cwd/ancestor, repo `AGENTS.md`/`CLAUDE.md` imports team-collab, the cwd is under a registered code/docs path, or the user asks for team-collab handoff/checkpoint/docs governance/Feishu automation. Do not use solely because a global config file exists.
Use when the user invokes `$digest`, asks for a multi-agent wave digest or progress summary, or asks "what's the status of the wave" / "where are things".
Use when the user invokes `$gate`, asks whether a PR/merge is ready, asks to gate-check or merge-gate a multi-agent task, or asks "can this merge?".
Use when the user invokes `$wave`, asks to start or enter a multi-agent wave, or asks to spin up / set up a wave for a batch of tasks coordinated across agents.
Use when the user invokes `$checkpoint`, asks for a checkpoint, or asks to update CURRENT/NEXT/RISKS/TODO without committing or pushing.
Use when the user invokes `$docs-refresh`, asks to update Obsidian project docs from a stale audit/dev record, or wants old docs archived while active docs become current.
| name | team-progress |
| requires_protocol | >=0.6.0,<0.7.0 |
| description | Use when the user invokes `$team-progress`, asks to sync recent progress from other team members, or asks who has blockers or PR/MR items needing review in a team-collab project. |
Codex-friendly command wrapper for concise team progress review. Supported Codex entry point:
$team-progress <time-window>
Examples: $team-progress 24h, $team-progress 3d, $team-progress since 2026-05-21 09:00.
team-collab-protocol skill and its references/team-progress.md flow.~/.codex/skills/team-collab-protocol/SKILL.md
team-collab install-skills --agent codex --force
If a future Codex version supports custom slash commands and /team-progress reaches the model as plain user text, handle it exactly the same way as $team-progress.