Standard collaboration patterns for all squad agents — worktree awareness, decisions, cross-agent communication
The English summary is being prepared. Showing the original description.
jguadagno/jjgnet-broadcast18Updated Aug 4, 2026
FreePublished on GitHub
agent-conduct
Shared hard rules enforced across all squad agents
The English summary is being prepared. Showing the original description.
See how to installFiles included (1)
- SKILL.md1.3 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
Context
Every squad agent must follow these two hard rules. They were previously duplicated in every charter. Now they live here as a shared skill, loaded once.
Patterns
Product Isolation Rule (hard rule)
Tests, CI workflows, and product code must NEVER depend on specific agent names from any particular squad. "Our squad" must not impact "the squad." No hardcoded references to agent names (Flight, EECOM, FIDO, etc.) in test assertions, CI configs, or product logic. Use generic/parameterized values. If a test needs agent names, use obviously-fake test fixtures (e.g., "test-agent-1", "TestBot").
Peer Quality Check (hard rule)
Before finishing work, verify your changes don't break existing tests. Run the test suite for files you touched. If CI has been failing, check your changes aren't contributing to the problem. When you learn from mistakes, update your history.md.
Anti-Patterns
- Don't hardcode dev team agent names in product code or tests
- Don't skip test verification before declaring work done
- Don't ignore pre-existing CI failures that your changes may worsen
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content.
The English summary is being prepared. Showing the original description.
jguadagno/jjgnet-broadcast18Updated Aug 4, 2026
Migrate API controller scope checks to framework-enforced authorization policies while preserving ownership checks.
The English summary is being prepared. Showing the original description.
jguadagno/jjgnet-broadcast18Updated Aug 4, 2026
api-dto-review
FreeReview API DTO implementations for contract/domain separation, mapping patterns, and REST compliance
The English summary is being prepared. Showing the original description.
jguadagno/jjgnet-broadcast18Updated Aug 4, 2026
Register shared claims transformation and hierarchical role policies in the API without breaking existing scope enforcement.
The English summary is being prepared. Showing the original description.
jguadagno/jjgnet-broadcast18Updated Aug 4, 2026
How to write comprehensive architectural proposals that drive alignment before code is written
The English summary is being prepared. Showing the original description.
jguadagno/jjgnet-broadcast18Updated Aug 4, 2026