Skip to content

feat: blanket @copilot delegation mode for implementation tasks #1677

Open

Description

@bradygaster

Summary

When Plan Activate creates implementation task issues, users should be able to opt into having all coding tasks assigned to @copilot automatically — instead of distributing across cast members.

Motivation

Customers want the option of saying "let @copilot do anything coding-related." Today the Lead triages each issue individually against @copilot's capability profile. There's no blanket delegation mode.

Proposed Design

Policy flag

Add a config option (in team.md or config.json):

<!-- copilot-implementation-mode: all-coding -->

Or in config.json:

{
  "copilotImplementationMode": "all-coding"
}

Values: "triage" (default — Lead evaluates per-issue), "all-coding" (blanket delegation).

Plan Activate behavior

When copilotImplementationMode: "all-coding":

  1. Task issues still get squad:{agent} labels for Squad tracking
  2. Additionally, issues get assigned to @copilot via GitHub assignment
  3. @copilot picks them up, creates copilot/* branches, opens draft PRs
  4. Squad agents shift to review-only — Lead reviews PRs, Tester validates

Squad agent role shift

With blanket delegation active:

  • Lead → reviews @copilot PRs, approves/rejects
  • Tester → validates @copilot output against acceptance criteria
  • Security → scans @copilot PRs for vulnerabilities
  • Docs → updates documentation based on @copilot changes

Prerequisites

  • copilot-setup-steps.yml must be configured in the repo
  • @copilot must be on the Squad roster (squad cast-member copilot)

Relationship

  • Extends the existing @copilot roster member support (.squad/templates/copilot-agent.md)
  • Touches Plan Activate mode in workflows/squad.md
  • Touches Lead triage logic in coordinator

Open Questions

  • Should there be a per-epic override? (e.g., "all coding except security-sensitive tasks")
  • Should @copilot PRs auto-request review from the Squad Lead?
  • How does this interact with the Reviewer Rejection Protocol when @copilot's PR is rejected?

Activity

  1. added
    gh-awGitHub Agentic Workflows integration
    triagedIssue has been triaged
    wave:3-laterWave 3 — backlog, future
    on Aug 24, 2026
  2. bradygaster commented on Aug 30, 2026

    @bradygaster
    CollaboratorAuthor

    Scope clarification (Ralph triage): This issue is distinct from \copilot-auto-assign\ (which routes GitHub issue assignment to Copilot). This feature requests a blanket capability-evaluation bypass — skipping the capability check that normally gates whether an agent proceeds with an implementation task. That is a different concern: auto-assign is about routing ownership; this is about suppressing the go/no-go gate for delegated tasks. Integration context: #1729 (review gate epic) and #1828 (reviewer lockout enforcement) are relevant if this bypass interacts with the review gate pipeline. Scope needs explicit clarification before implementation.

  3. added
    post-2.0Deferred until after the 2.0 line
    and removed
    wave:3-laterWave 3 — backlog, future
    on Nov 5, 2026
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

    enhancementNew feature or improvementgh-awGitHub Agentic Workflows integrationpost-2.0Deferred until after the 2.0 linepriority:p2Next sprinttriagedIssue has been triaged

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions