agent-conduct

To enforce shared governance rules across multiple squad agents, you can apply a centralized skill during charter creation and code reviews to prevent policy drift and ensure consistency.

The best way to prevent hardcoded agent names in CI configurations is to apply centralized governance rules that guard product logic and tests from depending on specific squad names.

Yes, you can use a single frontmatter-based entry point with a name and description for discovery, while loading a contextual body of governance rules directly into agent workflows.

Peer-review governance works during CI and test reviews by triggering peer-quality checks that promote validation and maintain an auditable history of rule enforcement across squads.

Yes, you need centralized governance rules to prevent policy drift, as consolidating hard cross-squad rules into a single reusable skill ensures all agent charters remain consistent.