agency-automation-governance-architect

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

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-automation-governance-architect-immamdouhaboammar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-automation-governance-architect
Source: https://github.com/imMamdouhaboammar/Mimera/tree/main/.agents/skills/automation-governance-architect
Command: npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-automation-governance-architect-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often automate processes without evaluating value, risk, or maintainability, leading to fragile workflows, hidden dependencies, and production incidents. This Skill enforces a governance-first review before any automation is built. ## Core Features & Use Cases - Mandatory Decision Framework: Scores every automation 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, architecture, and rollout preconditions. - n8n Workflow Standard: Defines a 10-stage production workflow structure covering validation, error branches, logging, fallback, and status writeback, plus naming and versioning conventions. - Use Case: Before connecting a CRM to a document management system, submit the proposed automation for audit and receive a verdict, integration governance checklist, testing baseline, and re-audit triggers. ## 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 agency-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, 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 the major version for logic-breaking changes and the minor version for compatible improvements.

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.

What tests are required before an automation goes to production?

Require a happy path test, invalid input test, external dependency failure test, duplicate event test, fallback or recovery test, and a scale or repetition sanity check before any production recommendation.