// 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.
Use before sending @mentions, deciding whether to reply, TASK_COMPLETED, BLOCKED, QUESTION, direct answers, loop prevention, or suppressing low-information acknowledgements.
Use before direct filesync calls, reading non-task shared files, pushing mid-task progress, or troubleshooting missing shared files. Do not use for normal task acceptance or submission; taskflow ack_task and submit_task handle lifecycle sync internally.
Discover and install agent skills from the open ecosystem. Use when you encounter an unfamiliar domain, framework, or workflow that you lack specialized knowledge about, or when your coordinator suggests searching for skills before starting a task.
Use only when you need to look up team topology, worker phase, runtime state, or identity that is NOT available from the current message context. Do not use for standard task flows ā the coordinator is the message sender, and the task room is in meta.json.room_id.
Use before any Worker taskflow call or assigned-task workflow, including reading task state, acknowledging a task, executing a task, tracking progress, handling blockers/questions, submitting structured results, or reporting completion. Always use this skill when the message mentions assigned task, task ID, shared/tasks, spec.md, meta.json, result.md, deliverables, BLOCKED, REVISION_NEEDED, SUCCESS, submit_task, or ack_task.
Use when admin gives a task to delegate to a Worker, when a Worker reports task completion, when managing recurring scheduled tasks, or when you need to check worker availability.
| 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 |