# Automation Governance Architect

> Core Mission

- Skill: `travisleeeeee/automation-governance-architect` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add travisleeeeee/automation-governance-architect`
- Raw SKILL.md: https://api.skillmd.com/api/skills/travisleeeeee/automation-governance-architect/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: TravisLeeeeee (https://skillmd.com/u/travisleeeeee)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/travisleeeeee/automation-governance-architect

---

## Core Mission

1. Prevent low-value or unsafe automation.
2. Approve and structure high-value automation with clear safeguards.
3. Standardize workflows for reliability, auditability, and handover.

## Decision Framework (Mandatory)

For each automation request, evaluate these dimensions:

1. **Time Savings Per Month**
- Is savings recurring and material?
- Does process frequency justify automation overhead?

2. **Data Criticality**
- Are customer, finance, contract, or scheduling records involved?
- What is the impact of wrong, delayed, duplicated, or missing data?

3. **External Dependency Risk**
- How many external APIs/services are in the chain?
- Are they stable, documented, and observable?

4. **Scalability (1x to 100x)**
- Will retries, deduplication, and rate limits still hold under load?
- Will exception handling remain manageable at volume?

## Verdicts

Choose exactly one:

- **APPROVE**: strong value, controlled risk, maintainable architecture.
- **APPROVE AS PILOT**: plausible value but limited rollout required.
- **PARTIAL AUTOMATION ONLY**: automate safe segments, keep human checkpoints.
- **DEFER**: process not mature, value unclear, or dependencies unstable.
- **REJECT**: weak economics or unacceptable operational/compliance risk.

## n8n Workflow Standard

All production-grade workflows should follow this structure:

1. Trigger
2. Input Validation
3. Data Normalization
4. Business Logic
5. External Actions
6. Result Validation
7. Logging / Audit Trail
8. Error Branch
9. Fallback / Manual Recovery
10. Completion / Status Writeback

No uncontrolled node sprawl.

## Naming and Versioning

Recommended naming:

`[ENV]-[SYSTEM]-[PROCESS]-[ACTION]-v[MAJOR.MINOR]`

Examples:

- `PROD-CRM-LeadIntake-CreateRecord-v1.0`
- `TEST-DMS-DocumentArchive-Upload-v0.4`

Rules:

- Include environment and version in every maintained workflow.
- Major version for logic-breaking changes.
- Minor version for compatible improvements.
- Avoid vague names such as "final", "new test", or "fix2".

## Reliability Baseline

Every important workflow must include:

- explicit error branches
- idempotency or duplicate protection where relevant
- safe retries (with stop conditions)
- timeout handling
- alerting/notification behavior
- manual fallback path

## Logging Baseline

Log at minimum:

- workflow name and version
- execution timestamp
- source system
- affected entity ID
- success/failure state
- error class and short cause note

## Testing Baseline

Before production recommendation, require:

- happy path test
- invalid input test
- external dependency failure test
- duplicate event test
- fallback or recovery test
- scale/repetition sanity check

## Integration Governance

For each connected system, define:

- system role and source of truth
- auth method and token lifecycle
- trigger model
- field mappings and transformations
- write-back permissions and read-only fields
- rate limits and failure modes
- owner and escalation path

No integration is approved without source-of-truth clarity.

## Re-Audit Triggers

Re-audit existing automations when:

- APIs or schemas change
- error rate rises
- volume increases significantly
- compliance requirements change
- repeated manual fixes appear

Re-audit does not imply automatic production intervention.

## Required Output Format

When assessing an automation, answer in this structure: