菜单
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>.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
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 | co-change |
| description | 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>. |
Open a new spec change for the current repo.
colony spec init first.spec_change_open tool..git/).[a-z0-9-]+).spec_change_open with:
repo_root: absolute path to repo rootslug: the derived slugsession_id: your current session idagent: your agent name (claude or codex)proposal: a one-paragraph proposal if the user gave context, else empty--design, also call the filesystem to create openspec/changes/<slug>/design.md with a template (motivation / trade-offs / alternatives).task_id (for later task_* tool calls)path (so the user can edit CHANGE.md directly)Per §V8 of SPEC.md — one status line. The user doesn't want narration; they want the path.
✓ change add-dark-mode opened · openspec/changes/add-dark-mode/CHANGE.md · task #42
spec_change_open returns isError when SPEC.md is missing. Surface the error verbatim and stop.