Coordinate parallel multi-agent workflows with mailbox-based planning and file edit locks.
npx skills add https://github.com/cassioalexandre/agf --skill team-bernie
Please help me install this Agent Skill. Skill: team-bernie Source: https://github.com/cassioalexandre/agf/tree/main/.agents/skills/Team%20Bernie Command: npx skills add https://github.com/cassioalexandre/agf --skill team-bernie
This skill solves the problem of getting multiple AI agents to collaborate safely and coherently on the same project without stepping on each other’s changes.
.antigravity/team/locks/ semaphores and requiring lock release after completion.Use the team-bernie skill to initialize Bernie’s team orchestration for your project, then ask for parallel tasks (e.g., backend + frontend + documentation) while Bernie manages approvals and lock-safe execution.
High-intent search queries and answers about installing and using this skill.
You can coordinate parallel AI agents by using a shared team state directory that tracks task dependencies and applies lock-based mutual exclusion. Agents must acquire file locks before editing and release them after completion to prevent conflicts.
Mailbox-based planning in multi-agent orchestration routes Action Plans from specialist agents to a central leader agent for review. The leader must approve each plan before specialists execute significant project changes.
Managing task dependencies across concurrent AI agents requires a shared team state directory that records task statuses and dependency tracking. This structure ensures dependent tasks wait for upstream completion before initiating execution.
Yes, you can run frontend, backend, and research AI agents concurrently on the same project. A leader agent broadcasts messages to align specialists, while planning approvals and file locks ensure changes are synchronized safely.
File locks protect multi-agent workflow execution by acting as semaphores that enforce mutual exclusion. They prevent multiple agents from writing to the same file simultaneously, requiring explicit lock release after task completion.
Yes, a shared state directory is required to synchronize agent team execution. It stores task status and dependency tracking data alongside lock semaphores, which are essential for coordinating parallel work and preventing conflicts.
lpjhelderCoordinate multiple workers on a shared task list via tmux-based orchestration.
richfremFinalize Spec-Kitty tasks into work-package prompts via the agent shim.
FISHers6Coordinate specialist agents with canonical task actions and CLI commands.
derHakenDispatch parallel agents to handle independent tasks without shared state.