---
title: "Workflow Architect"
type: source
tags: [agent, the-agency, workflow-design, process-engineering]
date: 2026-03-29
sources: [specialized-workflow-architect]
last_updated: 2026-04-20
---

## Source File
- [[raw/Agent/agency-agents/specialized/specialized-workflow-architect.md]]

## Summary
- 核心主题：Workflow Architect 负责把系统行为拆解为完整的工作流树，覆盖 happy path、分支条件、失败模式、恢复路径和交接契约
- 问题域：隐式流程、遗漏分支、未定义 handoff、cleanup 缺失、spec 与现实漂移
- 方法/机制：发现扫描、工作流注册表、步骤级分支建模、可观察状态定义、ABORT_CLEANUP、Reality Checker 校验
- 结论/价值：把流程设计从描述性文本提升为可实现、可测试、可审计的结构化规格

## Key Claims
- Workflow Architect 的核心职责不是写代码，而是定义系统必须如何表现
- 每个工作流都必须覆盖 happy path、validation failure、timeout、transient failure、permanent failure、partial failure 和 concurrent conflict
- 每个系统边界都必须定义 payload、success response、failure response、timeout 和 recovery action
- 任何创建资源的步骤都必须进入 cleanup inventory，并在 ABORT_CLEANUP 中有对应销毁动作
- Reality Checker 是工作流规范闭环的一部分，不能在未验证实现前标记 Approved

## Key Quotes
> "You think in trees, not prose."

> "A workflow that exists in code but not in a spec is a liability."

> "Every system boundary must have explicit payload schema, explicit success response, explicit failure response, timeout value, and recovery action."

## Key Concepts
- [[Workflow Architecture]]：以流程树建模系统行为的方法
- [[Claude Skills]]：将重复流程封装为可复用 SOP 的技术范式
- [[Process Optimization]]：通过重设工作流提升效率、质量与可靠性
- [[AI-powered Runbooks]]：将历史事件和最佳实践转为可执行运维手册
- [[Document Generation]]：将结构化规范与模板化产物自动化生成

## Key Entities
- [[The Agency]]：所属项目
- [[Workflow Architect]]：对应的 AI Agent 实体

## Connections
- [[The Agency]] ← contains ← [[Workflow Architect]]
- [[Claude Skills]] ← enables ← [[Workflow Architect]]
- [[Workflow Architecture]] ← defines ← [[Workflow Architect]]
- [[Process Optimization]] ← benefits_from ← [[Workflow Architect]]
- [[AI-powered Runbooks]] ← operationalizes ← [[Workflow Architect]]

## Contradictions
- 无明显冲突