メニュー
Coordinate repository work through Colony MCP. Use when an agent starts, resumes, chooses work, claims files, hands off work, records working state, or finishes a task in a repo where Colony tools are available.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Bucket Claude Code and Codex session tokens into Colony tasks and surface improvement suggestions. Use when the user runs `/co:tokens`, asks how many tokens a task spent, why a session got expensive, or what to change next time.
This skill should be used when building data processing pipelines with CocoIndex, a Python library for incremental data transformation. Use when the task involves processing files/data into databases, creating vector embeddings, building knowledge graphs, ETL workflows, or any data pipeline requiring automatic change detection and incremental updates. CocoIndex is Python-native (supports any Python types), has no DSL, and uses version 1.0.0 or later.
Validate, three-way-merge, and archive a colonykit change. Use when the user runs `/co:archive <slug>` or says the change is done. Atomic — either the archive and root-write both land, or neither does.
Execute the next §T task on the current colonykit change. Use when the user runs `/co:build` or asks you to proceed with the next task. Pulls cite-scoped context, executes, on test failure records via backprop gating.
Open a new colonykit spec change. Use when the user runs `/co:change <slug>` or asks to start a new proposal, delta, or change-in-flight. Creates openspec/changes/<slug>/CHANGE.md and opens a task-thread on spec/<slug>.
Read-only drift check across root SPEC.md, the active change's delta, and the code. Use when the user runs `/co:check` or asks whether the spec and code are in sync. Writes nothing.
| name | colony-mcp |
| description | Coordinate repository work through Colony MCP. Use when an agent starts, resumes, chooses work, claims files, hands off work, records working state, or finishes a task in a repo where Colony tools are available. |
Colony is a coordination surface you pull from when it helps — it does not run agents and never forces a ritual. It shows live branches, claims, handoffs, ready work, stale ownership, and compact memory so you avoid duplicate work. The steps below are a menu: use the parts that fit the task, skip the rest.
hivemind_context with agent, session_id, and repo_root.attention_inbox before choosing or resuming work.task_ready_for_agent to pick claimable plan work. Use task_list
only for browsing or debugging, not as the scheduler.task_accept_handoff before editing.If Colony MCP tools are unavailable, say so and continue with local git and repo inspection. Do not invent Colony state.
task_plan_claim_subtask when the task came from a
Colony plan.task_claim_file.task_note_working:
branch=<branch>; task=<task>; blocker=<blocker>; next=<next>; evidence=<evidence>.Claims are coordination warnings, not locks. If another fresh claim overlaps your edit, read the latest task thread and avoid overwriting unrelated work.
task_post.task_message for directed coordination when available.Before stopping, run git status and identify dirty files.