agent-conduct

You can enforce consistent agent governance by loading a centralized skill once at runtime that applies shared hard rules across all squad charters. This prevents duplication and ensures standardized behavior during both charter creation and daily operations.

To prevent hard-coded references in CI and tests, apply the Product Isolation Rule. This governance rule enforces agent-agnostic references, which maintains test stability and ensures CI configurations remain generic across different environments.

A Peer Quality Check is a governance rule that ensures tests and CI configurations remain generic and stable. It prevents hard-coded agent names and encourages agent-agnostic references to maintain reliability across squad operations.

You need to apply shared hard rules when creating or updating squad charters. Loading a centralized governance skill at this stage prevents hard-coded references and ensures consistent behavior across all squad agents from the start.

No, you do not need to configure rules separately for each agent. This skill is loaded once at runtime as a centralized governance solution, consolidating hard rules to prevent duplication and ensure consistent enforcement across all squads.

The centralized hard rules focus specifically on Product Isolation and Peer Quality Checks to prevent hard-coded references. They provide clear guidelines and anti-patterns to avoid, but are limited to governance scope and do not handle broader agent configuration.