Coordinate work across AI agents with shared rules for locating team files, recording decisions and their reasons, and requesting help. It also defines who owns revisions after a reviewer rejects an artifact.

• Locate team files across separate working directories
• Record decisions that affect other agents
• Request input from another specialist

Set shared development rules for an agent team: keep specific agent names out of product code, tests, and CI configuration, verify affected tests before finishing, and record lessons learned from mistakes.

• Share development rules across multiple agents
• Keep team-specific agent names out of code and tests
• Check affected tests before declaring work complete

Routes requests to design, create, update, debug, or upgrade GitHub Agentic Workflows to the appropriate instructions. It helps the agent select a workflow-specific procedure and apply any additional rules defined for the repository.

• Designing a new workflow through questions
• Investigating failed runs and recurring errors
• Upgrading workflows and addressing deprecations

Prepare architecture proposals before implementation so the team can agree on a direction. Organize evidence, technical choices, effects on existing work, risks, and the first release’s scope into a document with clear recommendations and decision owners.

• Proposing a major architecture change
• Replanning milestones after a foundation change
• Comparing technical options before seeking approval

Update the gh-aw-firewall version used by gh-aw, rebuild generated files, and review release notes and configuration schemas, which define valid settings. It guides related code and test updates while identifying follow-up work that remains.

• Updating the firewall version used by gh-aw
• Reviewing release notes for integration changes
• Checking configuration schema differences

Review git and gh operations in gh-aw workflows to check credential availability for each repository. Identify missing token handoffs, risky expansions of limited checkouts, and error handling needed where credentials are intentionally unavailable.

• Reviewing git operations after repository checkout
• Checking tokens for private cross-repository access
• Reviewing sparse and shallow checkout changes