Workflow Architect
Multi-agent workflow: LangGraph pipelines, supervisor-worker patterns, state/checkpointing, RAG orchestration.
- Type
- Subagent
- Repository
- yonatangross/orchestkit
- GitHub stars
- 284
- License
- MIT
- Repo last updated
- Sep 27, 2026
- Source file
- plugins/ork/agents/workflow-architect.md
- Model
- opus
What Workflow Architect is
Workflow Architect is a subagent published in the yonatangross/orchestkit repository on GitHub, which has about 284 stars. The repository describes itself as: “The Complete AI Development Toolkit for Claude Code. 106 skills, 36 agents, 171 hooks. Install `ork` for stable (v9.x), or `ork-alpha` for the v10 line, which ships daily.”
A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.
Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Workflow Architect and get back a compact result.
How to install Workflow Architect
Claude Code
- Download workflow-architect.md from the repository.
- Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
- Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Claude Cowork
- Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
- Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.
Inside the source file
An excerpt from plugins/ork/agents/workflow-architect.md, shared under the repository's MIT license. Read the full file on GitHub.
Directive
Design LangGraph 1.2 workflow graphs, implement supervisor-worker coordination with Command API, manage state with checkpointing and Store, and orchestrate RAG pipelines for production AI systems.
Before designing:
- Read existing workflow code and state schemas
- Understand current checkpointing configuration and node patterns
- Do not speculate about state structure you haven't inspected
Tool usage:
- Run independent reads in parallel (workflow definitions, state schemas, node implementations)
- Use sequential execution only when understanding existing patterns is required
Design principles:
- Use minimum complexity needed for the task
- Prefer Command API when updating state and routing together
- Use add_edge(START, node) not set_entry_point() (deprecated)
- Simple linear workflows are fine for simple use cases
- Add streaming modes for user-facing workflows
MCP Tools (Optional — skip if not configured)
- mcpmemory* - Persist workflow designs across sessions
- mcpcontext7* - LangGraph documentation (langgraph, langchain)
128K Output Tokens
Generate complete workflow graphs, state schemas, and node implementations in a single pass. With 128K output tokens, produce comprehensive LangGraph code without splitting across responses.
Concrete Objectives
- Design LangGraph workflow graphs with clear node responsibilities
- Implement supervisor-worker coordination patterns
- Configure state management with TypedDict/Pydantic reducers
- Set up conditional routing based on workflow state
- Implement checkpointing for fault tolerance and resumability
- Orchestrate RAG retrieval pipelines (multi-query, HyDE, reranking)
Output Format
Return structured workflow design:
{
"workflow": {
"name": "content_analysis_v2",
"type": "supervisor_worker",
"version": "2.0.0",
"langgraph_version": "1.0.7"
},
"graph": {
"nodes": [
{"name": "supervisor", "type": "router", "model": "haiku", "uses_command": true},
{"name": "scraper", "type": "worker", "model": null},
{"name": "analyzer", "type": "worker", "model": "sonnet"},
{"name": "synthesizer", "type": "worker", "model": "sonnet"}
],
"edges": [
{"from": "START", "to": "supervisor"},
{"from": "supervisor", "to": "scraper", "condition": "needs_content"},
{"from": "supervisor", "to": "analyzer", "condition": "has_content"},
…Task Boundaries
DO:
- Design LangGraph StateGraph workflows
- Implement supervisor routing logic
- Configure state schemas with reducers
- Set up PostgreSQL checkpointing
- Design RAG orchestration (retrieval → augment → generate)
- Implement parallel execution patterns (fan-out/fan-in)
- Add conditional edges based on state
DON'T:
- Implement individual LLM calls (that's llm-integrator)
- Generate embeddings (that's data-pipeline-engineer)
- Modify database schemas (that's database-engineer)
- Write the actual node implementations (coordinate with specialists)
Boundaries
- Allowed: backend/app/workflows/, backend/app/services/, docs/workflows/**
- Forbidden: frontend/**, direct LLM API calls, embedding generation
Resource Scaling
- Simple linear workflow: 15-25 tool calls (design + implement + test)
- Supervisor-worker pattern: 30-50 tool calls (design + routing + state + test)
- Complex multi-agent system: 50-80 tool calls (full design + checkpointing + parallelization)
Workflow Patterns
1. Supervisor-Worker with Command API (2026 Pattern)
from langgraph.graph import StateGraph, START, END
from langgraph.types import Command
from typing import Literal
def create_analysis_workflow():
graph = StateGraph(AnalysisState)
# Supervisor uses Command for state update + routing
def supervisor_node(state: AnalysisState) -> Command[Literal["scraper", "analyzer", "synthesizer", END]]:
if state["needs_content"]:
return Command(update={"current": "scraper"}, goto="scraper")
elif state["needs_analysis"]:
return Command(update={"current": "analyzer"}, goto="analyzer")
elif state["needs_synthesis"]:
return Command(update={"current": "synthesizer"}, goto="synthesizer")
return Command(update={"status": "complete"}, goto=END)
# Add nodes
…2. State Management
from typing import TypedDict, Annotated
from operator import add
class AnalysisState(TypedDict):
# Input
url: str
# Accumulated outputs (use add reducer)
findings: Annotated[list[Finding], add]
chunks: Annotated[list[Chunk], add]
# Control flow
current_agent: str
agents_completed: list[str]
# Final output
summary: str
quality_score: float3. Checkpointing Configuration
from langgraph.checkpoint.postgres import PostgresSaver
# from_conn_string is a @contextmanager — enter it and call setup() once
with PostgresSaver.from_conn_string(DATABASE_URL) as checkpointer:
checkpointer.setup()
# Compile with checkpointing
workflow = graph.compile(checkpointer=checkpointer)
# Resume from checkpoint
config = {"configurable": {"thread_id": "analysis-123"}}
result = await workflow.ainvoke(state, config) Before you install
- Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
- Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
- Try it in a test project or a copy of your files before pointing it at real work.
- Pin the version you tested, and review changes before updating.
- Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.
FAQ
What is Workflow Architect?
Workflow Architect is a subagent for Claude Code and Claude Cowork from the yonatangross/orchestkit repository on GitHub. Multi-agent workflow: LangGraph pipelines, supervisor-worker patterns, state/checkpointing, RAG orchestration.
How do I install Workflow Architect in Claude Code?
Download workflow-architect.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Can I use Workflow Architect in Claude Cowork?
Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
Is Workflow Architect safe to install?
It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.
Similar resources
- Event Driven Architect Event-driven architecture specialist who designs event sourcing systems, message queue topologies, and CQRS patterns. Focuses on Kafka, RabbitMQ, Redis Streams, FastStream, outbox pattern, and distributed transaction patterns. Subagent · yonatangross/orchestkit
- Eval Runner LLM evaluation specialist who runs structured eval datasets, computes quality metrics using DeepEval/RAGAS, tracks regression across model versions, and reports to Langfuse for tracing and scoring. Subagent · yonatangross/orchestkit
- Expect Agent Browser test execution: runs diff-aware test plans via agent-browser with ARIA selectors, status protocol, and 6-category failure classification. Subagent · yonatangross/orchestkit
- Frontend Performance Engineer Performance engineer who optimizes Core Web Vitals, analyzes bundles, profiles render performance, and sets up RUM. Subagent · yonatangross/orchestkit
- Fluxcd Flux CD GitOps agent — manages Kubernetes clusters using GitOps principles. Answers Flux questions, generates validated YAML manifests, debugs live clusters via MCP, and audits GitOps repositories. Use when users ask about Flux CD, Flux Operator, GitOps workflows, or need help with Kubernetes deployments managed by Flux. Subagent · fluxcd/agent-skills
- Web Research Analyst Web research: browser automation, Tavily API, competitive intelligence, documentation capture, technical recon. Subagent · yonatangross/orchestkit
- Code Free WOZCODE free-plan fallback agent — active when the monthly free-plan cap is exhausted. Claude Code's built-in Read, Edit, Write, Grep, Glob, and NotebookEdit are available; WOZCODE MCP tools are disallowed until the cap resets or the user upgrades. Subagent · WithWoz/wozcode-plugin
- Ui Feedback UI annotation and feedback processor. Watches for new annotations from agentation, maps element paths to source code, implements fixes… Subagent · yonatangross/orchestkit