hive-workflow

Create, update, and track git-backed hive cells across swarm workflows.

Updated Jan 14, 2026
One-click install
npx skills add https://github.com/primeinc/swarm --skill hive-workflow-primeinc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hive-workflow
Source: https://github.com/primeinc/swarm/tree/main/packages/opencode-swarm-plugin/examples/skill/hive-workflow
Command: npx skills add https://github.com/primeinc/swarm --skill hive-workflow-primeinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Hive provides a local-first, git-backed system for managing work items in AI swarm workflows. This skill offers best practices for creating, updating, and coordinating cells (bugs, features, tasks, epics) and ensures consistency across agents.

Core Features & Use Cases

  • Create and manage cells of types bug, feature, task, chore, epic with open/in_progress/blocked/closed states.
  • Epic management with linked subtasks and cross-team coordination.
  • Sync changes to a git-backed hive directory and track progress across sessions.
  • Swarm coordination guidance: load relevant skills like swarm-coordination and swarm-mail for end-to-end orchestration.

Quick Start

Load the hive-workflow skill and begin by creating an epic and a few tasks; move status as work progresses; finally close them and sync.

  • hive_create(type="epic", title="User Auth Overhaul", body="...")
  • hive_create(type="task", title="Implement OAuth2", parent="epic-id")
  • hive_update(id="hv-abc123", state="in_progress")
  • hive_close(id="hv-abc123", resolution="Fixed in commit ...")
  • hive_sync()

Frequently Asked Questions about hive-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track AI swarm work items with a git-backed issue tracker?

You can track AI swarm work items using a local-first, git-backed framework to create, update, and close cells. It applies to swarm workflows by decomposing work into epics and subtasks while maintaining persistent history across sessions.

What is the best way to manage epic and subtask decomposition for agent coordination?

Managing epic and subtask decomposition involves creating an epic cell and linking tasks to it using a parent identifier. This enables cross-team coordination and ensures traceability across multiple agents within the swarm workflow.

How do I sync issue tracking changes to a local git repository?

You sync issue tracking changes by executing a sync command that writes updates to a git-backed hive directory. This action persists cell lifecycle operations and tracks progress safely across different sessions.

Can I use local-first issue tracking for bugs, features, and chores in one workflow?

Yes, local-first issue tracking supports managing cells of types bug, feature, task, chore, and epic. Each cell transitions through open, in_progress, blocked, and closed states to ensure consistency across agents.

Does hive workflow require any specific tools for swarm orchestration?

Hive workflow recommends loading relevant skills like swarm-coordination and swarm-mail for end-to-end swarm orchestration. These complementary tools provide guidance for coordinating agents and managing communication across the workflow.

Why use a local-first issue tracker instead of a centralized database for AI agents?

A local-first issue tracker provides a git-backed system that ensures consistency across autonomous AI agents without relying on a centralized database. It satisfies cell lifecycle operations and enables safe collaboration with persistent history.

Related Skills