You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Coordinator prompt: add task context classification to acknowledgment #359
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
feat: add task context classification to coordinator acknowledgment
github-actions commentedon Mar 13, 2026
squad:verbal. Check.squad/team.md(or.ai-team/team.md) for valid member names.github-actions commentedon Mar 13, 2026
🏗️ 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:
squad:flightsquad:proceduressquad:eecomsquad:fidosquad:paosquad:capcomsquad:controlsquad:surgeonsquad:boostersquad:gncsquad:networksquad:retrosquad:incosquad:guidosquad:telemetrysquad:voxsquad:dskysquad:simssquad:handbooksquad:ralphsquad:copilotbradygaster commentedon Mar 13, 2026
📌 Brady requested this issue be assigned to @diberry (docs/UX triage). Pending collaborator invite to complete assignment.
feat: add task context classification to coordinator acknowledgment
feat: add task context classification to coordinator acknowledgment
feat: accessibility hardening and guidelines (github#359)