Add Automation Architect & Auditor (n8n) agent

[DKFuH]

Agent Information

Agent Name: Automation Architect & Auditor (n8n)
Category: specialized
Specialty: Governance-level n8n automation strategy, auditing, and standardization

Motivation

This adds a dedicated n8n-focused governance agent for evaluating, prioritizing, and safeguarding business automation initiatives. The agent emphasizes economic viability, stability, security, maintainability, and auditability over automation volume.

What Changed

• Added new agent: specialized/n8n-orchestrator-agent.md
• Added the agent to the Specialized Division table in README.md
• Updated visible agent count in README stats from 61 to 62

Testing

• Verified Markdown frontmatter and section structure
• Verified README link references the new file path
• Confirmed branch builds clean git history for review

Checklist

• Follows agent template structure
• Includes personality and voice
• Has concrete framework / output structure
• Defines success metrics
• Includes step-by-step workflow elements
• Proofread and formatted correctly

[msitarzewski]

Hey @DKFuH — thanks for putting this together! The automation governance angle is interesting and fills a gap we don't have covered yet.

A few things before we can merge:

1. Missing frontmatter fields — we now require emoji and vibe in agent frontmatter. emoji should be a single emoji character that represents the agent, and vibe is a one-liner that captures the agent's personality (see any existing agent for examples).

2. README edit — please drop the README changes from your PR. The agent count in there is already stale and we maintain it separately.

3. Length — at 444 lines this is one of the longest agents in the repo. Some sections read more like an SOP manual than a prompt agent personality. Would you be open to trimming it down? The best agents are opinionated and concise rather than exhaustive.

4. Naming consideration — the agent is tightly coupled to n8n in the filename and framing. Worth considering whether a more generic name like "Automation Governance Architect" (with n8n mentioned as a primary tool) would make it more broadly useful. Not a hard requirement — just something to think about.

Looking forward to the update!

[DKFuH]

Thanks for the detailed feedback - updated ✅

I addressed the requested changes:

1. Added the required frontmatter fields: emoji and vibe.
2. Removed README changes from this PR (PR now only contains the agent file).
3. Trimmed and tightened the content significantly to be more concise/opinionated.
4. Applied the naming suggestion by generalizing to Automation Governance Architect with n8n positioned as the primary orchestration tool.