mandos-operacao-cerebro-pycode

Define Slack operating conventions for multi-agent coordination and delegation.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill mandos-operacao-cerebro-pycode
Or copy as Structured Prompt for Agentโ–ผ
Please help me install this Agent Skill.
Skill: mandos-operacao-cerebro-pycode
Source: https://github.com/rafael-fae/agent-ops-worflow/tree/main/skills/operacao/mandos-operacao-cerebro-pycode
Command: npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill mandos-operacao-cerebro-pycode

SYSTEM DOCUMENTATION & REQUIREMENTS

๐Ÿ’ก This Skill includes references (resource) components.

What problem does it solve?

This Skill standardizes how a multi-agent team communicates, delegates, and reports in Slack so work does not fragment across sessions, channels, or threads.

Core Features & Use Cases

  • Channel Architecture: Defines team, cross-team, and response-channel rules for the Mac and OVH agent groups.
  • Mention Discipline: Enforces real Slack user-ID mentions, read-vs-respond behavior, and thread-only replies to prevent accidental bot chatter.
  • Operational Guardrails: Captures planning, delegation, model selection, task completion, and audit rules for day-to-day agent operations.
  • Use Case: A lead agent can use this Skill to coordinate planning, approval, delegation, execution, and reporting across multiple Slack-based agents without breaking command flow.

Quick Start

Use this skill to review the teamโ€™s Slack operating rules and produce the correct mention, thread, and delegation behavior for a new task.

Frequently Asked Questions about mandos-operacao-cerebro-pycode

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

FAQPage Schema
How do I coordinate multi-agent Slack operations without fragmenting work across threads?โ–ผ

Multi-agent Slack operations use standardized channel architecture, strict mention IDs, and thread-based delegation control to prevent work fragmentation. This ensures agents maintain command flow across team, cross-team, and response channels during planning, execution, and reporting.

How do I enforce thread-only replies to prevent accidental bot chatter in Slack?โ–ผ

To prevent accidental bot chatter, enforce read-vs-respond behavior and thread-only replies using strict operational guardrails. Agents must use real Slack user-ID mentions and adhere to thread-based delegation control within designated response channels.

What is the best way to route tasks across multiple Slack agents in a fleet?โ–ผ

Task routing across Slack agents requires defined operational guardrails for delegation and channel separation. A lead agent coordinates task routing, model selection, and execution by enforcing strict mention IDs and topology rules across designated team and cross-team channels.

Can I use channel separation to manage daily planning and cross-team orchestration for agent fleets?โ–ผ

Yes, channel separation manages daily planning and cross-team orchestration by defining distinct team, cross-team, and response channels. This architecture ensures agents follow operational guardrails for approval, execution, auditing, and reporting without overlapping conversations.

Do I need real Slack user-ID mentions for multi-agent delegation control?โ–ผ

Yes, real Slack user-ID mentions are required for multi-agent delegation control. Mention discipline enforces read-vs-respond behavior and thread-only replies, ensuring agents process approvals and execute tasks without triggering accidental chatter in wrong channels.