agent-conduct

To enforce consistent governance rules across multiple agent squads, you need a centralized policy that acts as a single source of truth. This prevents duplication and ensures uniform behavior across code, tests, and CI configurations.

Common anti-patterns when managing shared rules for agent teams include hardcoding agent names and experiencing reference drift across squads. Centralizing policy into a reusable governance skill helps teams avoid these configuration inconsistencies.

You codify hard rules for agents by defining metadata in YAML frontmatter and documenting patterns and anti-patterns. This allows automated loading and provides context-rich guidance for teams applying rules across workflows.

Agent behavior becomes inconsistent across different squads when shared hard rules are duplicated or decentralized. Applying a central governance skill ensures peer quality checks and product isolation policies are uniformly enforced.

Yes, you can apply product isolation policies across multiple squads without duplicating charters by using a central governance skill. It centralizes hard rules to ensure consistent behavior and reduce duplication across agent configurations.

You need a central governance skill for agent workflows whenever multiple squads contribute to code, tests, or CI configurations. It ensures shared hard rules are applied consistently and prevents reference drift across teams.