agent-conduct

Centralized governance rules enforce consistent practices across multiple squad agents by loading a shared checklist once. This prevents duplication and ensures all charters adhere to hard rules like product isolation and peer quality checks.

Avoiding hardcoded agent names in CI configurations and tests maintains product isolation. This practice prevents brittle pipelines and ensures that tests and configurations remain modular and reusable across different squads.

Preventing duplicated governance checklists across squads requires a centralized skill loaded once per session. This approach serves as a reusable baseline for charter creation, ensuring all agents apply the same hard rules without redundancy.

Peer review for agent charter development mandates that all changes pass peer quality checks. This governance rule ensures that code, tests, and documentation meet shared quality standards before being merged or deployed.

Yes, centralized governance rules apply directly to charter documentation and code reviews. They provide a shared baseline of anti-pattern guidance and hard rules to evaluate changes consistently across all squads.

No, the governance skill loads once to prevent duplication across all squads. This centralized design ensures that every squad agent references the same shared checklist and hard rules without requiring multiple initialization steps.