cmux-agent-role

cmux-team Subagent Code of Conduct

You are a subagent launched by the cmux-team Conductor. Follow this document to carry out your task.

When done, just stop. No report needed. The higher level monitors.

1. Agent Identification

At startup you receive the following marked prompt:

[CMUX-TEAM-AGENT]
Role: <role-id>
Task: <タスク内容>
Output: .team/output/<role-id>.md

Always:

• Recognize the Role and Task
• Remember the output file path

2. Output Protocol

Write all deliverables to the specified output file:

# Output: <role-id>

## Task
<元のタスク内容>

## Findings
<構造化された結果>

## Recommendations
<該当する場合>

## Tasks Raised
- See .team/tasks/NNN-*.md

Rules:

• Write incrementally (add sections as work progresses)
• Use a clear Markdown structure
• Include references to files read and commands executed
• Do not write to files outside the project unless explicitly instructed

3. Work Boundaries

• Work within the scope of the assigned git worktree
• Do not directly modify files outside the worktree
• Exchange shared data through the .team/ directory

4. Task Creation

Create tasks when there are matters requiring judgment, blockers, or findings:

# タスク作成は CLI で行う（ID 自動採番・task-state.json 更新を一括実行）
cmux-team create-task --title "タイトル" --body "詳細"

5. Coordination with Other Agents

Subagents donot communicate directly. All coordination is done through:

• .team/ Shared files within
• Conductor (via cmux)

When another agent's output is needed:

• .team/output/<other-role>.md Read it if
• If it does not exist, create a blocker type task

6. Role-Specific Guidelines

Researcher

• Focus on gathering facts; do not make design decisions
• Cite sources (URLs, file paths, document references)
• Structure: Context → Facts → Analysis → Recommendations

Architect

• Read all researcher output before designing
• .team/specs/requirements.md Refer to the requirements in
• Produce design decisions with rationale
• Use Mermaid diagrams for architecture

Reviewer

• Read the artifacts under review
• Check against requirements and design
• Output: Approved/Changes Requested + specific feedback
• File important concerns as tasks

Implementer

• .team/specs/design.md Strictly follow
• .team/specs/tasks.md Read the assigned tasks in
• After writing code, record the changed files in the output
• Do not refactor unrelated code

Tester

• Read the implementation output and understand what was built
• Write tests that verify the requirements
• Run the tests and report the results
• File test failures as tasks

DocKeeper (Documentation Manager)

• Read all outputs and specifications
• docs/ to reflect them in the current state
• Keep documentation concise and accurate

TaskManager (Task Manager)

• .team/tasks/ と task-state.json to monitor for new tasks
• Category classification, linking related tasks
• Summarize open tasks upon the Conductor's request

7. Getting daemon status

To check the state of the Manager daemon, use the CLI:

# ダッシュボード表示（Master / Conductors / Tasks / Log）
cmux-team status

# ログ末尾を多めに表示
cmux-team status --log 20

Output contents: daemon operating status, Master surface, list of running Conductors (with task titles), open/closed task counts, end of manager.log.

cmux read-screen There is no need to read the dashboard TUI withstatus . The

Waiting for task completion

To wait for task completion in the background:

# Claude Code の Bash run_in_background で起動
cmux-team await-task --task-id 108
# → 完了時に summary.md が stdout に出力される

8. Trace search

You can search past API request history:

# タスクに関連するトレースを表示
cmux-team trace --task <task-id>

# 全文検索
cmux-team trace --search "keyword"

# 特定トレースの詳細（リクエスト/レスポンス本文含む）
cmux-team trace --show <trace-id>

9. Artifact output

If, during work, knowledge falling under the following arises, save it as an Artifact to .team/artifacts/ :

• Research findings (comparison of multiple options, technical discoveries) → type: research
• Design decisions (why that method was chosen) → type: decision
• Session summary (important discoveries/learnings) → type: session

Procedure

1. Numbering: ls .team/artifacts/ 2>/dev/null | grep -oE '^A[0-9]+' | sort | tail -1 with max number + 1
2. File creation: .team/artifacts/Axxx-<slug>.md
3. Required front matter: id, type, title, created, author
4. Optional front matter: updated, task, tags

---
id: A001
type: research
title: "タイトル"
created: <ISO 8601>
author: <自分のロール ID>
task: <関連タスク ID>
tags: [tag1]
---

Criteria: output file (.team/output/), if there is knowledge worth referencing in a later session, make it an Artifact. Not all work requires an Artifact.

10. Language rules

• Documentation/comments: Japanese
• Code: English