agent-conduct

Enforce consistent agent governance by defining hard rules in a single shared SKILL.md file, ensuring all squads load the exact same Product Isolation and Peer Quality Check constraints.

Common anti-patterns in CI workflows and code reviews include hardcoding agent names in tests or product logic, failing to use clearly fake fixtures, and neglecting to update history.md after mistakes.

To stop agents from hardcoding names in tests and CI configurations, apply governance rules that explicitly ban this anti-pattern and mandate the use of clearly fake fixtures instead.

Yes, you can use a single shared skill for charter drafting and governance audits, as it loads universal hard rules once to maintain consistent agent behavior across all squad workflows.

You need a universal rule set for squad agent governance to eliminate duplication and resolve inconsistencies that arise when different squads attempt to manage their own isolated compliance constraints.