hive.colony-progress-tracker
Claim tasks, record step progress, and verify SOP gates in the colony SQLite queue. Applies when your spawn message includes a db_path field.
npx skills add aden-hive/hive --skill colony-progress-tracker --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
## Operational Protocol: Colony Progress Tracker **Applies when** your spawn message has `db_path:` and `colony_id:` fields. The DB is your durable working memory — tells you what's done, what to skip, which SOP gates you owe. Access via `terminal_exec` running `sqlite3 "<db_path>" "..."`. Tables: `tasks` (queue), `steps` (per-task decomposition), `sop_checklist` (hard gates). ### Claim: assigned task (check this FIRST) If your spawn message includes a `task_id:` field, the queen pre-assigned a specific row to you. Claim that row by id — **do not** use the generic next-pending pattern below: ```bash sqlite3 "<db_path>" <<'SQL' UPDATE tasks SET status='claimed', worker_id='<worker-id>', claim_token=lower(hex(randomblob(8))), claimed_at=datetime('now'), updated_at=datetime('now') WHERE id='<task_id>' AND status='pending' RETURNING id, goal, payload; SQL ``` Empty output → another worker raced you or the row is already done. Stop and report. Non-empty → that row is yours, proceed to "Load the plan". ### Claim: next pending (fallback when no task_id is assigned) If your spawn message did NOT include `task_id:` — you are a generic fan-out worker racing on a shared queue. Use the generic
- Operational Protocol: Colony Progress Tracker
- Claim: assigned task (check this FIRST)
- Claim: next pending (fallback when no taskid is assigned)
- Load the plan
- Execute a step
- MANDATORY: SOP gate check before marking task done
- Mark task done / failed
- Loop
- Errors + debug
- Anti-patterns (will break the queue)
sqlite3 "<db_path>" <<'SQL'
sqlite3 "<db_path>" "SELECT seq, id, title, status FROM steps WHERE task_id='<task-id>' ORDER BY seq;"
sqlite3 "<db_path>" "SELECT key, description, required, done_at FROM sop_checklist WHERE task_id='<task-id>';"
sqlite3 "<db_path>" "UPDATE steps SET status='in_progress', worker_id='<worker-id>', started_at=datetime('now') WHERE id='<step-id>';"
sqlite3 "<db_path>" "UPDATE steps SET status='done', evidence='<what you did>', completed_at=datetime('now') WHERE id='<step-id>';"
sqlite3 "<db_path>" "SELECT key, description FROM sop_checklist WHERE task_id='<task-id>' AND required=1 AND done_at IS NULL;"
sqlite3 "<db_path>" "UPDATE sop_checklist SET done_at=datetime('now'), done_by='<worker-id>', note='<why>' WHERE task_id='<task-id>' AND key='<key>';"
sqlite3 "<db_path>" "UPDATE tasks SET status='done', completed_at=datetime('now'), updated_at=datetime('now') WHERE id='<task-id>' AND worker_id='<worker-id>';"
Unrecoverable failure:What does the hive.colony-progress-tracker skill do?
Claim tasks, record step progress, and verify SOP gates in the colony SQLite queue. Applies when your spawn message includes a db_path field.
How do I install it?
Run `npx skills add aden-hive/hive --skill colony-progress-tracker --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aden-hive/hive, a repository with 10,850 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.