From c7ce014eac69077d67d3c2dc1deedf9a0c1f6a4c Mon Sep 17 00:00:00 2001 From: Godopu Date: Fri, 10 Jul 2026 09:34:07 +0900 Subject: [PATCH] docs: enforce markdown file-based task delegation and result delivery in MULTI_AGENT_RULES.md --- .agents/MULTI_AGENT_RULES.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/.agents/MULTI_AGENT_RULES.md b/.agents/MULTI_AGENT_RULES.md index 28730c3..199b49f 100644 --- a/.agents/MULTI_AGENT_RULES.md +++ b/.agents/MULTI_AGENT_RULES.md @@ -118,9 +118,12 @@ To ensure that agents running in TMUX environments do not lose debug logs or pre 2. **Loop Snapshot**: For long-running agent sessions (5 minutes or more), periodically (e.g., every 30 seconds) scan the viewport and append the incremental data to `/tmp/pane-snap.txt`. 3. **Post-job Capture**: Capture the complete pane state one final time immediately after a job completes or returns an error to preserve the entire execution trajectory. -### 📄 Handling Long Briefing Instructions -- Sending long instructions or prompts (hundreds of lines) sequentially via TMUX `send-keys` or input buffers can overwhelm the agent's TUI, leading to lost characters or truncated paragraphs. -- **Resolution**: If instructions are long, write them separately to a file path (e.g., `/tmp/brief-.md`) and send a simplified execution command to the agent: `"Read /tmp/brief-... and execute"`. +### 📄 Markdown-Based Workflow & Communication (마크다운 기반 협업 및 결과 전달) +- **Core Principle**: To prevent TUI character loss, truncation, and layout breakage during sequential input typing, all collaborative workflows must favor file-based markdown communication. +- **Rules & Protocols**: + - **Exception**: Extremely simple prompts (e.g., "Re-evaluate", "Check status", "Proceed") of 1 or 2 lines may be sent directly via tmux input buffers. + - **Task Delegation**: All detailed task briefs, specifications, and instructions must be written to a local Markdown file (e.g., `.mam/jobs/brief-.md` or a workspace path) first. The sender then issues a simple trigger command: `"Read and execute."` + - **Result Reporting & Feedback**: All detailed review results, design proposals, implementation reports, and audit comments must be saved as Markdown files. The recipient reads these files directly from disk instead of relying on truncated terminal screen captures. ### ⏱️ Timeout Configuration & Alignment Rules - **Job Execution Limits (`timeout_sec` & `idle_timeout_sec`)**: Each job independently manages its overall execution timeout (`timeout_sec`, default 3600s) and idle timeout without receiving messages (`idle_timeout_sec`, default 120s).