Works with the AI tools you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseOpenClawOpenClaw+21 more

    Enterprise Automation Architect — Production Workflow Design & Reliability

    1

    The problem Teams “automate the happy path” and discover duplicates, missed revokes, and silent API failures in production.

    $18

    Secure checkout via Stripe

    30-day refund guarantee

    Converts to your local currency at checkout

    Security scanned
    Enterprise Automation Architect — Production Workflow Design & Reliability

    Enterprise Automation Architect — Production Workflow Design & Reliability

    Example session with this skill installed

    Process: CampusAccess — after-hours building access exceptions

    Manual today

    1. ServiceNow request (building, rooms, window, reason)
    2. Clerk checks Workday employment active
    3. Clerk checks LMS safety training complete
    4. Clerk creates temporary badge grant in access-control system
    5. Slack #campus-security + email requester
    6. BSL-2 / lab after 10pm needs lab director signature (PDF today)
    7. Morning revoke often forgotten → orphan grants

    Volume: ~80/week, ~200/week at semester start
    SLA: 4 business hours for standard buildings
    Constraints: reuse Temporal; no secrets in repo; no orphan grants after window

    Ask: full production automation architecture (design mode). Do not execute.

    • Read your context and instructions
    • Compiled the enterprise automation architect
    • Generated the document

    Enterprise Automation Architecture

    1. Decision Summary

    FieldValue
    ProcessCampusAccess after-hours access exceptions
    ModeDesign
    Paradigmevent-driven (ServiceNow)
    Scale bandmedium at semester peaks
    Build vs buyOrchestrate on Temporal + modular adapters
    MaturityNEEDS-HARDENING

    2. Human-automation boundary (excerpt)

    StepVerdict
    Workday + LMS checksAUTOMATE
    Standard building grantAUTOMATE (after checks)
    Lab / BSL-2 after 10pmKEEP-MANUAL path with director APPROVE
    Revoke after windowAUTOMATE (compliance)
    Policy waiversKEEP-MANUAL

    3–4. Paradigm & build recommendation

    Event-driven async workflow (not nightly batch). Reuse campus Temporal for
    durability, approval waits, and revoke timers. Thin adapters for ServiceNow,
    Workday, LMS, access control, Slack/email — not a second iPaaS.

    5–6. Contracts & reliability

    • Grant create: effectively-once via idempotency_key = ticket_id
    • Webhook: at-least-once with dedupe
    • Notify: at-most-once (never block grant on Slack failure)
    • Exception tree: inactive/untrained → auto-deny; access auth fail → escalate;
      lab after 22:00 → park for APPROVE; revoke fail → escalate + orphan report

    7–8. Security & HITL

    Threats: stolen creds, over-privileged bot, webhook spoofing, PII in logs.
    Secrets manager only. Least-privilege grant/revoke role.
    HITL: lab-after-10pm director APPROVE; standard path AUTO when policy passes.

    9–10. Observability & rollout

    Metrics: auto-approve rate, time-to-grant, orphan_grants_count, revoke failures.
    SLO: 4h standard decisions; zero orphans older than 24h.
    Rollout: Shadow (simulate) → Canary (one non-lab building) → Full (labs stay APPROVE).

    11–14. ROI, testing, runbook, maturity path

    Labor assumption ~20 clerk hours/week; payback often 1–2 semesters if validated.
    Tests: policy, idempotency, revoke timer, chaos on access API.
    Runbook: detect → triage by ticket_id → recover → communicate.
    To PRODUCTION-READY: confirm OpenAPI maps, orphan scanner, director UX, shadow period.

    15. JSON

    Full Automation Architecture JSON (boundary, adapters, steps, threats, slo, rollout,
    cost_model, testing, runbook, assumptions).

    enterprise-automation-architect-producti.pdf

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    What you get

    Design a new multi-system business automation from a process descriptionDecide AUTOMATE vs ASSIST vs KEEP-MANUAL for each stepChoose build vs buy vs orchestrator (Temporal / Airflow / n8n / SaaS)Harden a brittle automation (retries, dedupe, exception tree)Plan shadow → canary → full rollout with rollbackBuild a cost/ROI case versus manual effort

    About this skill

    The problem

    • Teams “automate the happy path” and discover duplicates, missed revokes, and silent API failures in production.
    • Not every step should be automated — high-judgment and high-liability steps need human-in-the-loop design up front.
    • Build-vs-buy and orchestrator choice are often made by habit, not by volume, durability, and ops ownership.
    • Leadership asks for ROI and SLA accountability, but the design never defined metrics or a safe rollout.

    What it does

    • Classifies the automation paradigm (batch, scheduled, event-driven, streaming, human-triggered) and scales the design to real volume.
    • Draws a human-automation boundary: AUTOMATE, ASSIST, or KEEP-MANUAL per step with reasoning.
    • Recommends build vs buy vs orchestrate (e.g. Temporal, Airflow, n8n, SaaS) with a clear rationale.
    • Designs modular adapters with data contracts and delivery guarantees (at-most / at-least / effectively-once).
    • Specifies idempotency, retries, rate limits, and an exception decision tree (retry / escalate / skip / compensate / park).
    • Builds a security threat model, secrets plan, and HITL gates (AUTO / CONFIRM / APPROVE).
    • Defines observability + business metrics + SLA/SLOs, a shadow → canary → full rollout, cost/ROI, testing, runbook, and a maturity path to production.

    Frameworks & tools

    • Orchestrators and integration platforms commonly used in enterprises (Temporal, Airflow, n8n, iPaaS) plus custom adapters.
    • Works across ERP, ITSM, HRIS, LMS, messaging, access control, and other SaaS/API systems you name.
    • Compatible with Claude Code, Cursor, Codex CLI, OpenClaw, and other SKILL.md agents — no live execution required for design.

    Why this beats prompting it yourself

    • Forces the hard questions: what not to automate, what needs approval, how duplicates are prevented.
    • Typed delivery guarantees and exception trees instead of “add a retry.”
    • Security and PII logging constraints designed with the workflow, not bolted on later.
    • Rollout stages with exit criteria and rollback — not a big-bang cutover.
    • ROI and SLOs stated with explicit assumptions, not invented precision.
    • Maturity verdict with a concrete path (e.g. NEEDS-HARDENING → PRODUCTION-READY).

    How to install

    Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.

    ~30 seconds
    1. 1

      Download the ZIP

      Free skills download straight away. Paid skills unlock right after purchase.

    2. 2

      Unzip into your skills folder

      Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.

    3. 3

      Ask your agent to use it

      Restart the agent if it was already running. It picks the skill up automatically - no config needed.

    Skills folder by agent

    Click the path to copy it. Create the folder if it does not exist yet.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    30-day refund

    Not a fit? Get your money back

    Trust & safety

    Security scanned

    Verified clean 1 month ago

    • Passed all security checks, Safe to install

    Listed1 month ago

    What's inside

    Frequently Asked Questions