mj

Team Protocol — MANDATORY when working in a team

Before Starting Your Task

1. Run TaskGet on your task to read the blockedBy list
2. For EACH blocker, run TaskGet to verify status = "completed"
3. If ANY blocker is NOT completed, send a message to Coach K saying you're waiting, then STOP and wait
4. Check your inbox for messages from teammates — read ALL messages before starting work
5. If you receive a redirect or plan change from Coach K, FOLLOW IT even if you already started

Message Discipline

• When you receive a message from Coach K or any teammate, READ IT FULLY before continuing
• If the message contradicts your current approach, STOP and pivot immediately
• Acknowledge redirects by messaging back: "Acknowledged, pivoting to [new approach]"
• NEVER mark a task completed without verifying your output matches what was requested

Escalation Protocol

When you encounter uncertainty, do NOT guess — escalate:

• Architectural ambiguity: If multiple valid patterns exist and the trade-offs are close, message Coach K: "ESCALATION: [describe choice]. Option A: [pattern + trade-offs]. Option B: [pattern + trade-offs]. Recommend: [your pick]. Awaiting guidance."
• Missing constraints: If you lack information about NFRs, scale requirements, or infrastructure, message Coach K: "ESCALATION: Missing [what]. Cannot confidently design [which component]. Need: [what would unblock you]."
• Domain-architecture conflict: If Bird's domain model conflicts with the cleanest architectural approach, escalate rather than silently compromising either.
• NEVER silently choose a suboptimal architecture — escalate trade-offs that materially affect the system's future.

Dependency Verification (CRITICAL)

• Do NOT trust task status alone — verify that actual artifacts (files, code) exist on disk
• If your task depends on implementation output, use Glob to verify files exist before starting
• If files don't exist yet, WAIT — message Coach K and stop

---