Skip to content

Coordinator prompt: add task context classification to acknowledgment #359

Closed

Description

@diberry

Problem

When a user sends a message, the coordinator acknowledges with agent names and work descriptions, but doesn't classify whether the message is a continuation of existing work, a new unrelated task, or a related pivot. This makes multi-turn sessions feel linear.

Proposed Change

Add a Task Context Signal requirement to the Acknowledge Immediately section in .github/agents/squad.agent.md. Before the agent launch table, the coordinator must emit one of:

  • 🔗 Continuing — same task thread as previous messages
  • 🆕 New task — unrelated to previous work
  • 🔀 Related pivot — connected to previous work but a different concern

Scope

  • Prompt-only change to .github/agents/squad.agent.md
  • No code changes, no build impact, no test changes

UX Before/After

Before:

🔧 EECOM — fixing the auth handler

After:

🔗 Continuing your auth work

🔧 EECOM — fixing the auth handler

Activity

  1. added a commit that references this issue on Mar 12, 2026
    a5fa048
  2. github-actions commented on Mar 13, 2026

    @github-actions
    Contributor

    ⚠️ No squad member found matching label squad:verbal. Check .squad/team.md (or .ai-team/team.md) for valid member names.

  3. github-actions commented on Mar 13, 2026

    @github-actions
    Contributor

    🏗️ Squad Triage — Flight (Lead)

    Issue: #359 — Coordinator prompt: add task context classification to acknowledgment
    Assigned to: FIDO (Quality Owner)
    Reason: Issue relates to testing/quality work

    @copilot evaluation: 🔴 Not suitable — issue involves work outside the coding agent's capability profile.

    Team roster:

    • Flight (Lead) → label: squad:flight
    • Procedures (Prompt Engineer) → label: squad:procedures
    • EECOM (Core Dev) → label: squad:eecom
    • FIDO (Quality Owner) → label: squad:fido
    • PAO (DevRel) → label: squad:pao
    • CAPCOM (SDK Expert) → label: squad:capcom
    • CONTROL (TypeScript Engineer) → label: squad:control
    • Surgeon (Release Manager) → label: squad:surgeon
    • Booster (CI/CD Engineer) → label: squad:booster
    • GNC (Node.js Runtime) → label: squad:gnc
    • Network (Distribution) → label: squad:network
    • RETRO (Security) → label: squad:retro
    • INCO (CLI UX & Visual Design) → label: squad:inco
    • GUIDO (VS Code Extension) → label: squad:guido
    • Telemetry (Aspire & Observability) → label: squad:telemetry
    • VOX (REPL & Interactive Shell) → label: squad:vox
    • DSKY (TUI Engineer) → label: squad:dsky
    • Sims (E2E Test Engineer) → label: squad:sims
    • Handbook (SDK Usability) → label: squad:handbook
    • Ralph (Work Monitor) → label: squad:ralph
    • @copilot (Coding Agent) → label: squad:copilot

    To reassign, remove the current squad:* label and add the correct one.

  4. bradygaster commented on Mar 13, 2026

    @bradygaster
    Collaborator

    📌 Brady requested this issue be assigned to @diberry (docs/UX triage). Pending collaborator invite to complete assignment.

  5. added 2 commits that reference this issue on Mar 14, 2026
    0d54051
    75c25c3
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

    go:needs-researchNeeds investigationpriority:p2Next sprintsquadSquad triage inbox — Lead will assign to a membertype:featureNew capability

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions