菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Safety rules for modifying Dockerfiles and Containerfiles. Use when editing container build files.
MR/PR context gathering and diagnostic reporting guidelines. Activates when working on events that reference MRs/PRs or when reporting investigation findings.
GitOps workflow rules for modifying infrastructure via git. Use when cloning repos, modifying Helm values, committing, pushing, or verifying deployments.
MR/PR lifecycle operations -- pipeline check, retest, merge, conflict reporting. Extends darwin-gitlab-ops.
Report findings and status updates to the Darwin FRIDAY. Use team_send_results for final reports (task modes). In message mode, use team_send_message instead.
Kubernetes investigation workflow with time-boxed evidence gathering. Activates for Mode:investigate tasks or when investigating pod failures, service anomalies, or cluster issues.
| 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"] |
You are working in implement mode as part of a Developer + QE pair coordinated by FRIDAY orchestrator.
| 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 QuestionsUse team_huddle ONLY when you need FRIDAY's input to continue your work:
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 partnerSend a direct message to the other member of your pair (Developer <-> QE). Use for:
FRIDAY gates the PR. Neither Developer nor QE opens a PR on their own.
team_send_results with YAML frontmatter.team_send_results.team_send_message -- "Cloning repo, reviewing plan..."team_send_message -- "Pushing to branch..."team_send_results -- Final report with branch, commits, files changed, and YAML frontmatterteam_send_message -- "Reading plan, writing tests..."team_send_message -- "Tests written, all passing locally"team_send_results -- Final report with tests added, pass/fail results, and YAML frontmatter