Can this skill help with deprecated code?

Yes, it specifically instructs agents to avoid outdated 'bd' and 'cass' references in favor of the newer swarm and hivemind toolsets.

What does the file reservation system do?

It prevents agents from overwriting each other's work by requiring agents to reserve files before edits and release them upon completion.

Does it support testing workflows?

Yes, it enforces a red-green-refactor testing discipline and requires agents to explicitly state if tests are absent or out of scope.

How does this skill handle different AI models?

It defines specific interaction styles for GPT-5.2-code (minimalist/strict) and Opus 4.5 (brief rationales/phased sections) to leverage their respective strengths.

Swarm Coordination Guidance

Name: Swarm Coordination Guidance
Author: joelhooks

byjoelhooks

•

359

Collaboration Tools

Establishes persistent rules and model-specific behaviors for multi-agent swarm coordination and standardized tool usage.

About

This skill provides a foundational framework for OpenCode swarm agents, ensuring consistent behavior across different AI models like GPT-5.2-code and Opus 4.5. It enforces strict instruction priorities, manages resource reservations through file locking, and standardizes subtask spawning workflows. By providing clear guidance on tool usage and output formatting, it prevents common errors related to deprecated references and helps maintain a disciplined testing workflow during complex, multi-agent development tasks.

Key Features

Strict output formatting for concise, action-oriented responses
Enforced instruction hierarchy (System > Developer > User > Agents)
Model-specific behavior optimization for GPT-5.2-code and Opus 4.5
Automated file reservation management with TTL-based locking
359 GitHub stars
Standardized swarm subtask spawning and worker handoffs

Use Cases

Migrating legacy agent workflows away from deprecated toolsets to the hivemind ecosystem
Ensuring consistent code quality and testing discipline across swarm-driven tasks
Coordinating multiple AI agents on a single codebase without file conflicts

About

Key Features

Strict output formatting for concise, action-oriented responses
Enforced instruction hierarchy (System > Developer > User > Agents)
Model-specific behavior optimization for GPT-5.2-code and Opus 4.5
Automated file reservation management with TTL-based locking
359 GitHub stars
Standardized swarm subtask spawning and worker handoffs

Use Cases

Migrating legacy agent workflows away from deprecated toolsets to the hivemind ecosystem
Ensuring consistent code quality and testing discipline across swarm-driven tasks
Coordinating multiple AI agents on a single codebase without file conflicts