darwin-team-huddle

name	darwin-team-huddle
description	Team coordination for implement and test modes. Developer and QE use team_send_results for final reports, team_huddle for mid-task questions to FRIDAY.
roles	["developer","qe"]
modes	["implement","test"]

Implement Mode Communication

You are working in implement mode as part of a Developer + QE pair coordinated by FRIDAY orchestrator.

Tool Usage

Tool	When to use	Who receives
team_send_results	Final report -- deliver your completed work with YAML frontmatter (reasoning + assessment + optional steps)	FRIDAY (final deliverable)
team_huddle	Mid-task questions that need FRIDAY input before you can continue	FRIDAY (blocks until reply)
team_send_message	Progress updates while working	FRIDAY UI (informational only)
team_send_to_teammate	Coordinate with your Dev/QE partner	Teammate's inbox
team_read_teammate_notes	Check what your partner sent you	Your inbox

team_send_results -- Final Report (all modes)

Use team_send_results to deliver your final report when your work is complete. This is FRIDAY's primary input for deciding the next action.

Your report MUST include YAML frontmatter with reasoning (required), assessment (your judgment), and steps (optional):

---
reasoning: "All changes implemented, tests passing on branch fix/evt-xxx"
steps:
  - id: verify
    agent: qe
    summary: "Verify changes before merge"
---

## Developer Report
Branch: fix/evt-xxx
Commit: abc1234
Files changed: 3

Without reasoning in frontmatter, team_send_results will reject your report.

team_huddle -- Mid-Task Questions

Use team_huddle ONLY when you need FRIDAY's input to continue your work:

• "Should I modify the Helm values or just the application code?"
• "The tests require a running database -- should I mock or use the live instance?"
• "CI failed on an unrelated test -- should I rebase or ignore?"

Sends a message to FRIDAY and blocks until FRIDAY replies. If no reply arrives, continue your work and deliver your report via team_send_results.

Do NOT use team_huddle for your final report -- use team_send_results.

team_send_to_teammate -- Coordinate with your partner

Send a direct message to the other member of your pair (Developer <-> QE). Use for:

• Shared branch coordination ("I pushed 3 commits, pull before you push")
• File conflict warnings ("I'm editing reviews.py, don't touch it")
• Handoff signals ("My tests are committed, your turn to open the PR")

Team Workflow -- PR Gate

FRIDAY gates the PR. Neither Developer nor QE opens a PR on their own.

1. Developer implements code changes, commits to the feature branch. Does NOT open a PR.
2. Developer delivers final report via team_send_results with YAML frontmatter.
3. FRIDAY dispatches QE to verify.
4. QE writes tests, commits to the same feature branch, delivers report via team_send_results.
5. FRIDAY reviews both outputs and tells Developer to open the PR.

Developer Workflow

1. team_send_message -- "Cloning repo, reviewing plan..."
2. ... implement changes ...
3. team_send_message -- "Pushing to branch..."
4. ... commit and push (do NOT open PR) ...
5. team_send_results -- Final report with branch, commits, files changed, and YAML frontmatter

QE Workflow

1. team_send_message -- "Reading plan, writing tests..."
2. ... write tests, commit to same feature branch ...
3. team_send_message -- "Tests written, all passing locally"
4. team_send_results -- Final report with tests added, pass/fail results, and YAML frontmatter