agent-conduct

Enforce shared governance rules for consistent, testable squad agent work.

2|Updated Apr 21, 2026
One-click install
npx skills add https://github.com/elbruno/md-to-slides --skill agent-conduct-elbruno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-conduct
Source: https://github.com/elbruno/md-to-slides/tree/main/.copilot/skills/agent-conduct
Command: npx skills add https://github.com/elbruno/md-to-slides --skill agent-conduct-elbruno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent agent behavior and fragile coordination by centralizing non-negotiable governance rules that must be followed across all squad agents.

Core Features & Use Cases

  • Product Isolation Rule: Ensures tests, CI workflows, and product code never depend on specific agent names from particular squads, using generic or parameterized fixtures instead.
  • Peer Quality Check: Requires validating changes by running existing tests for touched files and being mindful of pre-existing CI failures.
  • Use Case: When integrating a change to shared product logic, use these rules to avoid hardcoded squad-specific assumptions and to confirm the update doesn’t break the current test suite.

Quick Start

Use the agent-conduct skill to check your draft agent plan and updates against the Product Isolation Rule and Peer Quality Check before you finalize.

Frequently Asked Questions about agent-conduct

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent hardcoded agent names from breaking CI pipelines and test suites?

Product isolation prevents tests and CI workflows from depending on specific squad agent names by requiring generic or parameterized fixtures. This keeps pipelines consistent and testable across teams without leaking agent identity into assertions.

What are agent governance rules for shared product code changes?

Agent governance rules for shared product code require avoiding hardcoded squad-specific assumptions and validating changes by running the existing test suite for touched files. This centralizes non-negotiable standards to keep squad agent work consistent and testable across teams.

How do I validate test suite changes for touched files without breaking existing CI?

Validate test suite changes for touched files by running existing tests for those specific files while being mindful of pre-existing CI failures. This peer quality check confirms your updates do not break the current test suite before finalizing.

Can I use parameterized fixtures instead of squad-specific agent identities in CI configuration?

Yes, you can and should use parameterized fixtures instead of squad-specific agent identities in CI configuration. The product isolation rule requires avoiding hardcoded agent-name dependencies to ensure workflows remain generic and testable across teams.

Why does agent identity leak into test assertions and how do I stop it?

Agent identity leaks into test assertions when specific squad agent names are hardcoded into test logic. Stop this leakage by applying product isolation rules that enforce the use of generic or parameterized fixtures for all tests and CI workflows.