agent-conduct

To enforce consistent governance rules across multiple agents, centralize hard policies into a single source to eliminate duplicated constraints scattered across individual agent charters.

Removing hardcoded agent names from CI configs and tests enforces product isolation, allowing generic, non-namespaced references that prevent brittle dependencies and improve maintainability across squads.

Common anti-patterns when managing squad agent conventions include directly naming specific agents in code, skipping test suite verification, and failing to update history.md to reflect changes.

Centralize agent governance by applying shared hard rules across all squad agents, replacing duplicated constraints in charters with a single governance source for code and documentation.

Yes, this governance approach works for code, tests, CI configurations, and documentation, applying centralized validation and anti-hardcoding policies uniformly across all project assets.