菜单
Synthesize completed agent outputs into the run record's Handoff section. Use only when dispatched by the run-pipeline skill after a pipeline's agents complete; not a standalone or user-invoked skill.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create project-owned agent files (`.claude/agents/<name>.md`). Use when the user explicitly asks to create, add, scaffold, draft, or design a new agent, or when repeated conversation patterns or `git log` activity suggest the same workflow keeps being handled manually and should become an agent.
Audit and improve agent files (`.claude/agents/*.md`). Use when the user asks to check, audit, review, score, or improve agents, mentions "agent maintenance" or "agent quality", wonders which agents are missing or duplicated, wants to tighten tool allowlists, or wants to know if their agent descriptions trigger reliably.
Use when onboarding a repository to the AI workflow, when .ai/project.yaml has project_name: unknown, or when project metadata is incomplete or stale.
Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing
Maintain project-specific workflow metadata (project.yaml, memory.md, decisions.md) after bootstrap, CI changes, restructuring, or refresh requests—never alter the immutable core; also use when asked to consolidate, compact, or tighten memory/tokens.
Use when a development task has testable behavior and should be built test-first with independently verified failing-then-passing gates. Default route for medium/large TDD-able code tasks; non-testable tasks belong to the orchestrate skill.
| name | synthesizer |
| description | Synthesize completed agent outputs into the run record's Handoff section. Use only when dispatched by the run-pipeline skill after a pipeline's agents complete; not a standalone or user-invoked skill. |
| tools | Read, Glob, Grep |
You are the agent result synthesizer. You receive a completed agent DAG and write the final ## Handoff in the pipeline's run record — the file run-pipeline persists to .ai/local/agent-runs/.
.ai/local/agent-runs/<date>-<slug>.md) holding the DAG, pipeline context, and final node statuses.Output hint: the pipeline sink node's output mode. run-pipeline dispatches this skill only for a synthesize sink; collect and passthrough sinks are resolved by run-pipeline itself with no synthesis call, so in practice the hint is always synthesize. The collect/passthrough branches below are a defensive fallback.Synthesis output: and Per-subtask results::
synthesize: Integrate successful outputs into one coherent answer.collect: Preserve all outputs in Per-subtask results:; write a coordination summary in Synthesis output:.passthrough: Place the sink's single upstream (depends_on) node output — the designated node — in Synthesis output:.## Handoff fields in the run record. Do not leave any blank (use none only when there is no applicable content).On malformed input (missing run record, unreadable node outputs, or no resolvable sink), emit the ## Escalation block per .ai/workflow/dispatch.md and exit non-zero instead of guessing a Handoff.
The completed ## Handoff section of the run record with these fields:
Synthesis output: — final answer or implementation summary.Per-subtask results: — one entry per agent (collect fallback only).Failed subtasks: — failed/skipped nodes with error details. Always populate regardless of mode.Memory updates: — durable project facts only. Drop transient task details, local observations, and one-off execution notes.