メニュー
Activate when the user asks to create a new project, view project status, manage epics/stories/tasks, set execution priority, or query an agent's workload. Also activate when scheduling work as a project task with a cron (future execution).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Activate for ANY request involving specialist delegation — single or multi-step. Contains the complete orchestration SOP: plan-and-confirm format, sequential execution rules, how to write a complete `request` argument, recovery from errors, retry limits, file delivery rules, and output presentation.
Activate when a multi-agent orchestration goes wrong. Contains: recovery from `ValueError: Tool '<name>' not found`, the full forbidden-tool reference for each specialist, retry limits and abandon criteria, recovery if you accidentally invoked two specialists in parallel, and the catalogue of historically-reproduced mistakes. Pair with `multi-agent-chain` (the always- loaded core skill) — that one has the happy-path rules; this one has the escape hatches.
Use when delegating report generation, PDF creation, chart visualization, or data interpretation to the business analysis expert. Load this skill before calling `business_analysis(request='...')` so you know what to send, what it returns, and which tools are internal to that specialist (and must NEVER be called directly).
Use when delegating any task to the coding expert — Python scripting, data analysis, SVM / ML algorithms, file I/O, package installation, git operations, or running tests. Load this skill before calling `coding(request='...')` so you know what to send and how to read the response.
Use when a task involves database operations — SQL queries, schema inspection, data retrieval, record insertion/update/deletion, or database health checks. Load this skill before calling `database(request='...')`. IMPORTANT: This specialist may not be deployed — check the registered tool spec first.
Run before marking any task as done. Parses the task spec for output file paths and verifies each file actually exists on disk. If any required file is missing, requeues the task instead of closing it. Skip for tasks with no file output.
| name | project-management |
| description | Activate when the user asks to create a new project, view project status, manage epics/stories/tasks, set execution priority, or query an agent's workload. Also activate when scheduling work as a project task with a cron (future execution). |
When user asks to start a long-term project or explicitly requests project tracking:
create_epic(user_id, title, description) — one epic per projectcreate_story(epic_id, user_id, title, priority) — one story per major phasecreate_project_task(epic_id, user_id, title, spec, story_id, assigned_agent, priority) — one task per unit of workupdate_task_queue(user_id, assigned_agent, [task_id_1, task_id_2, ...]) — set execution orderAfter setting the queue, tasks with status=queued are automatically picked up by agents.
Note:
update_task_queueis for scheduled / queued work only. For immediate execution, always call the matching specialist agent tool directly (e.g.coding(request='...')). See Section 4.1 of the main instruction.
get_epic_detail(epic_id)get_agent_queue(user_id, assigned_agent)get_epics(user_id, status="all")status=done when complete, leaving a TaskComment with type=result.assess-and-register): you manually call update_task_status(task_id, "done") and add_task_comment.update_story(story_id, status="done").If user wants a one-time task executed at a future date (not recurring):
create_project_task(... cron="<expression>", ...) with cron set to fire onceupdate_task_queue to place it in the agent's queueFor recurring automated jobs → activate create-regular-work skill instead.