Skip to content

Squad file/name best practices #1997

Closed as not planned
Closed as not planned

Description

@diberry

If we intend to have more than one squad and intend to use it in GH CP app or VSCode, where we want each squad to have a unique name, should we update the name for ./github/agents/squad.agent.md. Or should we copy that file into a new filename and then change the name so that the file name isn't checked during an upgrade.

Activity

  1. bradygaster commented on Sep 24, 2026

    @bradygaster
    Collaborator

    Closing — this is a support/design question rather than a backlog item, and it's already answered by current design: .github/agents/squad.agent.md is a fixed path at the git root (one per repo), and per-squad differentiation happens through team.md/roster/state content, not by renaming or copying the agent file. Renaming it would break the upgrade path's file-based detection. If multiple distinct squads per single repo/app becomes a real requirement, that's better scoped as its own design issue (possibly folding into #2069, the new Squad specification RFC) rather than left as an open question here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions