メニュー
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.
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.
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 | co-archive |
| description | 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. |
Archive a completed change and merge its §S delta into the root SPEC.md.
x (done). If not, refuse and list the remaining tasks.openspec/changes/<slug>/CHANGE.md §T, confirm all rows are x.spec_archive with:
repo_root, slug, session_id, agentstrategy: default three_way. Pass last_writer_wins only if the user explicitly accepted conflicts.status: archived — print archived_path, applied delta count, and any conflicts that were resolved.status: refused — print the conflict list and tell the user to either resolve manually or re-run with --strategy last_writer_wins.If the response includes non-empty conflicts[]:
root_modified_since_base — root changed since /co:change opened. The safe move is to tell the user: someone else edited SPEC.md; re-open the change against the current root, or use last_writer_wins at your own risk.delta_removes_cited_row — the change removes a §V row that something else still cites. This is usually a mistake in the delta; advise editing the change rather than forcing the archive.unknown_target — the delta targets a section that doesn't accept deltas (e.g. G. or C.). Edit the change.One line on success:
✓ archived add-dark-mode · 7 deltas applied · openspec/changes/archive/2026-04-24-add-dark-mode/
spec_archive stages the archive move in a temp path, writes the new root, then atomically renames. A crash mid-call leaves either the pre-archive state or the fully-archived state. Don't build a "retry after partial archive" path — there is no partial archive.