メニュー
Use when admin asks to start a multi-worker project, when a Worker @mentions you with task completion in a project room, when project plan changes are needed, or when a blocked task needs resolution.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | project-management |
| description | Use when admin asks to start a multi-worker project, when a Worker @mentions you with task completion in a project room, when project plan changes are needed, or when a blocked task needs resolution. |
A project has: a Project Room (Matrix), a plan.md (single source of truth), a meta.json, and individual task files under shared/tasks/{task-id}/.
shared/projects/{project-id}/
├── meta.json
└── plan.md
[ "${HICLAW_YOLO:-}" = "1" ] || [ -f ~/yolo-mode ]. In YOLO mode you MUST auto-confirm in create-project.md Step 1c; never post a "please confirm" question, the admin will not reply and the project stalls forever. See references/create-project.md Step 0.references/plan-format.md as the canonical formatRead the relevant doc before executing. Do not load all of them.
| Situation | Read |
|---|---|
| Admin asks to start a new project | references/create-project.md |
| Need to assign a task or handle completion | references/task-lifecycle.md |
| Need plan.md / result.md format | references/plan-format.md |
| Blocked task, plan changes, mid-project onboarding, headcount request, heartbeat monitoring | references/plan-changes.md |
Discover and call MCP Server tools via the mcporter CLI. Use when your coordinator notifies you about new MCP tools, or when you need to call external APIs. Includes workflow for generating skill documentation for new MCP servers.
Use when TEAMS.md Communication Contract needs detailed routing: Channel / Room Selection Protocol, Requester Report Delivery Protocol, or Message Tool Protocol. It resolves current session vs Team Room vs assignment room vs requester reply_route vs external channel, and explains when to use the message MCP tool. Do not use it to choose Quick Task or Project Work, create rooms, delegate tasks, check results, or accept project state.
Use for TeamHarness shared workspace paths, explicit filesync operations, and shared project/task artifact boundaries.
Use to understand TeamHarness team roles, responsibility boundaries, and who owns project, task, runtime, and control-plane work.
Use only after Project Work mode is selected, before TeamHarness projectflow calls, project DAG or Loop planning, ready-node resolution, iteration recording, project files, result acceptance, or project progress updates.
Use only after Project Work mode is selected, when a TeamHarness Leader delegates ready project nodes, writes task specs, checks Worker results, and routes completion or blocker messages.