packages/opencode-swarm-plugin/examples/skill/hive-workflow/SKILL.md
Issue tracking and task management using the hive system. Use when creating, updating, or managing work items. Use when you need to track bugs, features, tasks, or epics. Do NOT use for simple one-off questions or explorations.
npx skillsauth add joelhooks/swarm-tools hive-workflowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Hive is a local-first issue tracking system designed for AI agents. This skill provides best practices for effective cell management.
NOTE: For swarm workflows, combine this skill with swarm-coordination from global-skills/.
| Type | When to Use |
| --------- | --------------------------------------- |
| bug | Something is broken and needs fixing |
| feature | New functionality to add |
| task | General work item |
| chore | Maintenance, refactoring, dependencies |
| epic | Large initiative with multiple subtasks |
- "Fix null pointer exception in UserService.getProfile()"
- "Add dark mode toggle to settings page"
- "Migrate auth tokens from localStorage to httpOnly cookies"
- "Fix bug" (too vague)
- "Make it better" (not actionable)
- "stuff" (meaningless)
## Problem
[Clear description of the issue or need]
## Expected Behavior
[What should happen]
## Current Behavior
[What currently happens, for bugs]
## Proposed Solution
[How to fix/implement, if known]
## Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
## Notes
[Any additional context, links, or constraints]
open → in_progress → closed
↓
blocked (optional)
hive_update(id: "hv-abc123", state: "in_progress")
Use when you start working on a cell.
hive_close(id: "hv-abc123", resolution: "Fixed in commit abc1234")
Use when work is complete.
hive_update(id: "hv-abc123", state: "blocked", body: "Blocked by #hv-xyz789")
Use when you can't proceed due to a dependency.
hive_query(state: "open", type: "bug")
hive_query(search: "authentication")
hive_query(limit: 10, sort: "updated")
Epics are containers for related work:
---
type: epic
title: User Authentication Overhaul
---
## Objective
Modernize the authentication system
## Subtasks
- [ ] #hv-001: Implement OAuth2 provider
- [ ] #hv-002: Add MFA support
- [ ] #hv-003: Migrate session storage
- [ ] #hv-004: Update login UI
hive_create(type: "epic", title: "User Auth Overhaul", body: "...")
hive_create(type: "task", title: "Implement OAuth2", parent: "epic-id")
1. **One cell per logical unit of work** - Don't combine unrelated fixes
2. **Update state promptly** - Keep cells reflecting reality
3. **Add context in body** - Future you will thank present you
4. **Link related cells** - Use `#hv-id` references
5. **Close with resolution** - Explain how it was resolved
6. **Use labels** - `priority:high`, `area:frontend`, etc.
Cells sync with git:
hive_sync() to commit and push to remoteWhen working in a swarm:
1. Load `swarm-coordination` skill with `skills_use(name="swarm-coordination")`
2. Create epic with `hive_create_epic()` (atomic operation)
3. Coordinator assigns cells to worker agents
4. Workers load relevant skills based on subtask type
5. Close cells as subtasks complete
6. Close epic when all subtasks done
7. Sync with `hive_sync()` (MANDATORY at session end)
- `type: "bug"` → Load `testing-patterns` for regression tests
- `type: "feature"` → Load `system-design` for architecture
- `type: "chore"` → Load `testing-patterns` if refactoring
- `type: "epic"` → Load `swarm-coordination` for decomposition
development
Patterns for testing code effectively. Use when breaking dependencies for testability, adding tests to existing code, understanding unfamiliar code through characterization tests, or deciding how to structure tests. Covers seams, dependency injection, test doubles, and safe refactoring techniques from Michael Feathers.
tools
Principles for building reusable coding systems. Use when designing modules, APIs, CLIs, or any code meant to be used by others. Based on "A Philosophy of Software Design" by John Ousterhout. Covers deep modules, complexity management, and design red flags.
development
Multi-agent coordination patterns for OpenCode swarm workflows. Use when working on complex tasks that benefit from parallelization, when coordinating multiple agents, or when managing task decomposition. Do NOT use for simple single-agent tasks.
development
Meta-skill for generating new skills with proper format and structure. Use when creating new skills for the swarm system or when agents need to generate skill scaffolds. Ensures skills follow conventions (frontmatter format, directory structure, bundled resources).