result-aggregation

Purpose

Aggregate and format results from multiple parallel agent executions into concise, scannable output.

When to Use

• After parallel agent execution completes
• When ecomode is active
• For batch operation summaries
• When reporting multi-agent task results

Aggregation Formats

Standard Batch Format

[Batch Complete] {completed}/{total}
├── {agent}: {icon} {summary}
├── {agent}: {icon} {summary}
└── {agent}: {icon} {summary}

Detailed Batch Format

[Batch Complete] {completed}/{total}

[1] {agent-name}
    Status: {success|failed|partial}
    Target: {file/path}
    Result: {summary}

[2] {agent-name}
    Status: {success|failed|partial}
    Target: {file/path}
    Result: {summary}

Error Summary Format

[Batch Complete] {completed}/{total} ({failures} failed)

Failures:
├── {agent}: {error summary}
└── {agent}: {error summary}

Successes:
├── {agent}: ✓ {summary}
└── {agent}: ✓ {summary}

Status Icons

Icon	Status	Use When
✓	Success	Task completed successfully
✗	Failed	Task failed with error
⚠	Warning	Completed with warnings
⏳	Pending	Still in progress
⊘	Skipped	Task was skipped

Aggregation Rules

1. Ordering

order:
  - Failed results first (need attention)
  - Warnings second
  - Successes last
  - Within category: alphabetical by agent

2. Summary Length

ecomode_on:
  max_length: 50 characters
  truncate_with: "..."

ecomode_off:
  max_length: 200 characters
  allow_multiline: true

3. Grouping

group_by:
  - status (success/failed/warning)
  - agent_type (when mixed types)
  - target_path (when same agent, different targets)

Integration

With Secretary

Secretary receives:
  - List of agent results
  - Ecomode status
  - User display preferences

Secretary outputs:
  - Aggregated summary using this skill
  - Individual details if requested

With Ecomode

When ecomode active:
  - Use compact format
  - One line per agent
  - Icons for status
  - Truncate long summaries

Examples

Code Review Batch

[Batch Complete] 4/4

├── lang-golang-expert: ✓ src/main.go - 2 issues (1 naming, 1 error handling)
├── lang-python-expert: ✓ scripts/*.py - Clean
├── lang-rust-expert: ⚠ lib/core.rs - 1 unsafe block flagged
└── lang-typescript-expert: ✓ web/app.tsx - 3 suggestions

Agent Creation Batch

[Batch Complete] 3/4 (1 failed)

✗ lang-kotlin-expert: Skill not found: kotlin-best-practices
✓ lang-golang-expert: Agent created at .claude/agents/lang-golang-expert.md
✓ lang-python-expert: Agent created at .claude/agents/lang-python-expert.md
✓ lang-rust-expert: Agent created at .claude/agents/lang-rust-expert.md

Audit Batch

[Batch Complete] 5/5

Agents Audited:
├── mgr-creator: ✓ All refs valid
├── mgr-updater: ✓ All refs valid
├── mgr-supplier: ⚠ 1 deprecated ref
├── lang-golang-expert: ✓ All refs valid
└── lang-python-expert: ✓ All refs valid

Summary: 5 agents checked, 1 warning

Artifact Channel Read Pattern

R006 Artifact Channel Protocol을 소비하는 표준 패턴. 병렬 에이전트가 각자 .claude/outputs/sessions/{date}/{skill}-{HHmmss}.md에 결과를 작성하면, result-aggregation이 경로 N개를 받아 단일 요약을 생성합니다.

Tool: Writing artifacts under .claude/outputs/

Under mode: "bypassPermissions", subagents write directly to .claude/outputs/sessions/ with the Write tool — direct .claude/** writes are permitted (CC v2.1.121+, #1101). No /tmp staging or script wrapping is needed. Read-only Bash on .claude/outputs/ (e.g., cat, head, wc) is allowed for verification.

Reference: R006/R010 sensitive-path handling (direct .claude/** write under bypassPermissions), #1101.

입력 형식

paths = [
  ".claude/outputs/sessions/2026-04-24/agent1-100200.md",
  ".claude/outputs/sessions/2026-04-24/agent2-100300.md",
  ...
]

집계 규칙

1. 각 경로를 Read 도구로 읽음 (본문 inline 전달 금지 — R006 원칙 준수)
2. 파일별 요약 추출 (status + key findings)
3. 단일 요약으로 압축 — R013 ecomode Aggregation Format 재사용

참조

• R006 MUST-agent-design.md Artifact Channel Protocol (source contract)
• R013 SHOULD-ecomode.md Deep Insight Context Handoff Pattern (budget 맥락)