Automation Governance Architect

Audits business automation requests and issues verdicts with n8n workflow architecture standards.

2|Updated May 21, 2026
One-click install
npx skills add https://github.com/tcvdog/agency-agents-hermes --skill automation-governance-architect-tcvdog
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Automation Governance Architect
Source: https://github.com/tcvdog/agency-agents-hermes/tree/main/specialized/automation-governance-architect
Command: npx skills add https://github.com/tcvdog/agency-agents-hermes --skill automation-governance-architect-tcvdog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often automate processes just because it is technically possible, leading to fragile workflows, hidden dependencies, and production incidents. This Skill evaluates every automation request against value, risk, and maintainability criteria before any implementation begins. ## Core Features & Use Cases - Mandatory Decision Framework: Scores each request on time savings, data criticality, external dependency risk, and scalability from 1x to 100x volume. - Structured Verdicts: Issues one of five rulings (APPROVE, APPROVE AS PILOT, PARTIAL AUTOMATION ONLY, DEFER, REJECT) with rationale and rollout preconditions. - n8n Workflow Standard: Enforces a 10-stage production workflow structure covering validation, logging, error branches, and fallback paths, plus naming and versioning conventions. - Use Case: A manager proposes syncing CRM leads to a scheduling tool via n8n. The Skill audits the integration's source-of-truth clarity, failure modes, and economics, then returns a pilot-only verdict with required tests and monitoring. ## Quick Start Use the Automation Governance Architect to evaluate this process for automation and return a verdict, rationale, architecture recommendation, implementation standard, and rollout preconditions.

Frequently Asked Questions about Automation Governance Architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide whether a business process should be automated?▼

Evaluate four dimensions: recurring time savings per month, data criticality, external dependency risk, and scalability from 1x to 100x volume. The Skill maps these scores to a verdict of approve, pilot, partial automation, defer, or reject.

What structure should a production n8n workflow follow?▼

A production n8n workflow should follow ten stages: trigger, input validation, data normalization, business logic, external actions, result validation, logging, error branch, fallback recovery, and status writeback. Uncontrolled node sprawl is not permitted.

How should I name and version n8n workflows?▼

Use the pattern [ENV]-[SYSTEM]-[PROCESS]-[ACTION]-v[MAJOR.MINOR], such as PROD-CRM-LeadIntake-CreateRecord-v1.0. Increment major versions for logic-breaking changes and minor versions for compatible improvements.

What tests are required before deploying an automation to production?▼

Require six tests: happy path, invalid input, external dependency failure, duplicate event, fallback or recovery, and a scale/repetition sanity check. No workflow should be marked done without documentation and test evidence.

When should an existing automation be re-audited?▼

Re-audit when APIs or schemas change, error rates rise, volume increases significantly, compliance requirements change, or repeated manual fixes appear. Re-audit does not imply automatic production intervention.

When should a process not be automated?▼

Reject automation when economics are weak or operational and compliance risk is unacceptable. Defer when the process is immature, value is unclear, or dependencies are unstable, and keep human checkpoints for critical data flows.