Menu
Multi-agent task coordination via Git-backed Markdown. Claim tasks, prevent collisions, track history with automatic commits.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | tick-md |
| description | Multi-agent task coordination via Git-backed Markdown. Claim tasks, prevent collisions, track history with automatic commits. |
| homepage | https://tick.md |
| metadata | {"openclaw":{"emoji":"✅","kind":"skill"}} |
Multi-agent task coordination via Git-backed Markdown
Coordinate work across human and AI agents using structured TICK.md files. Built on Git, designed for natural language interaction, optimized for multi-agent workflows.
npm install -g tick-md
cd your-project
tick init
tick status
tick add "Build authentication" --priority high --tags backend
tick claim TASK-001 @yourname
tick done TASK-001 @yourname
npm install -g tick-mcp-server
Add to your MCP config (e.g., ~/Library/Application Support/Claude/claude_desktop_config.json):
{
"mcpServers": {
"tick": {
"command": "tick-mcp",
"args": [],
"env": {}
}
}
}
The MCP server exposes all CLI commands as tools:
tick_init - Initialize a projecttick_add - Create taskstick_claim - Claim tasks for your agenttick_done - Mark tasks completetick_status - Get project overviewtick_list - Query and filter taskstick_comment - Add progress notes---
meta:
project_id: my-project
id_prefix: TASK
next_id: 4
updated: 2026-02-07T15:30:00-05:00
---
### TASK-001 · Build user authentication
\`\`\`yaml
id: TASK-001
status: in_progress
priority: high
claimed_by: @claude-code
assigned_to: @claude-code
created_by: @gianni
created_at: 2026-02-07T10:00:00-05:00
updated_at: 2026-02-07T15:30:00-05:00
tags: [backend, auth]
depends_on: []
blocks: [TASK-002, TASK-003]
history:
- ts: 2026-02-07T10:00:00 who: @gianni action: created
- ts: 2026-02-07T15:30:00 who: @claude-code action: claimed
\`\`\`
> Build JWT-based authentication with refresh tokens
By default, every mutation creates a git commit:
[tick] TASK-001 claimed by @claude-code
[tick] TASK-001 completed by @claude-code
[tick] TASK-003: created
Control with flags:
--commit - Force commit--no-commit - Skip commit.tick/config.ymlbacklog - Not ready to starttodo - Ready to claimin_progress - Being worked onreview - Awaiting reviewblocked - Waiting on dependenciesdone - CompletedThe CLI uses .tick.lock to prevent concurrent edits. When an agent claims a task, it acquires the lock. Other agents see the task is claimed and can't modify it.
# Human creates tasks
tick add "Build landing page" --priority high --tags frontend --assign @claude-code
tick add "Write launch email" --priority medium --tags content --assign @content-bot
tick add "E2E tests" --priority medium --tags qa --depends-on TASK-001
# AI agent picks up work
tick claim TASK-001 @claude-code
tick comment TASK-001 @claude-code --note "Built responsive landing with hero section"
tick done TASK-001 @claude-code
# Another agent auto-triggers
tick claim TASK-003 @qa-bot
tick done TASK-003 @qa-bot --skip-review
Edit .tick/config.yml:
git:
auto_commit: true # Auto-commit on mutations (default: true)
commit_prefix: "[tick]"
push_on_sync: false
locking:
enabled: true
timeout: 300
agents:
default_trust: full
require_registration: false
tick claim TASK-XXX @yourbotnametick comment TASK-XXX @yourbotname --note "Status update"tick done TASK-XXX @yourbotnametick list --blocked to find blocked tasksStep-by-step guide for coordinating multiple OpenClaw bots via TICK.md.
gh repo create yourorg/project-tasks --private
cd project-tasks
npx tick-md init
git add -A && git commit -m "init" && git push
cd /data/.openclaw/workspace
git clone git@github.com:yourorg/project-tasks.git tasks
cd tasks && npx tick-md status
## ✅ Task Coordination (TICK.md)
I coordinate with other agents via TICK.md in `./tasks/`.
### Before starting work:
1. `cd tasks && npx tick-md sync` — get latest
2. `npx tick-md list --status backlog --priority high` — find available work
3. `npx tick-md claim TASK-XXX @mybotname` — claim before working
4. `npx tick-md done TASK-XXX @mybotname` — mark complete
### Rules:
- **Never work on a task claimed by another agent**
- **Always claim before starting**
- **Sync before and after work**
## Task Sync (TICK.md)
- [ ] Sync tasks: `cd tasks && npx tick-md sync`
- [ ] Check for my work: `npx tick-md list --claimed-by @mybotname --status in_progress`
- [ ] Check for available tasks: `npx tick-md list --status backlog --priority high`
Each bot needs SSH access to the shared repo. Generate a deploy key on each server:
ssh-keygen -t ed25519 -C "botname@tasks" -f ~/.ssh/tasks_deploy -N ""
cat ~/.ssh/tasks_deploy.pub
# Add this to repo Settings → Deploy Keys (with write access)
Configure git to use it:
cd tasks
git config core.sshCommand "ssh -i ~/.ssh/tasks_deploy -o IdentitiesOnly=yes"
After any tick mutation, push changes:
cd tasks && git push
Or use tick sync which handles pull + push automatically.
tick-md on npmtick-mcp-server on npm