explaingit

ankitclassicvision/agent-automation-creator

16HTMLAudience · pm founderComplexity · 2/5ActiveSetup · easy

TLDR

A written framework and 34-page PDF spec for designing AI-inclusive workflows by mapping the process first, assigning runtimes second, and applying AI discipline last.

Mindmap

mindmap
  root((agent-automation-creator))
    Inputs
      Existing process
      Workflow nodes
      Agent pitch or vendor doc
    Outputs
      Process map
      Runtime tags
      HTML grading report
    Use Cases
      Audit an AI pitch
      Grade an automation
      Design a workflow
    Tech Stack
      HTML
      PDF spec
      AgentTwin skill
      Claude Code

Things people build with this

USE CASE 1

Grade a vendor agent pitch against a 57-item checklist before signing a contract.

USE CASE 2

Map an internal process and tag each step as deterministic, closed-loop AI, assisted AI, or human only.

USE CASE 3

Generate a two-view HTML report with a letter grade for executives plus a builder-level process map.

USE CASE 4

Apply the Bounded, Grounded, Gated, Observed, Governed rules to decide where to put a human in the loop.

Tech stack

HTMLPDFMarkdownClaude Code

Getting it running

Difficulty · easy Time to first run · 30min

Repo is mostly documents; reading the 34-page PDF spec before applying the checklist is the main time cost.

In plain English

AAC, short for Agent Automation Creator, is a written framework for designing workflows that include AI. The author's argument is that most AI projects fail because teams pick the AI tool first and then bend a process around it. AAC flips the order. You map the process, then assign the right kind of runtime to each piece of work, and only then add AI discipline where AI is actually doing the work. The framework has three layers and the author says you must build them bottom up. Layer 1 is the process map, drawn at three levels of detail: small work elements with one verb each, nodes that group work with a single owner, and the full process graph with triggers and queues. Layer 2 is runtime assignment, where every work element is tagged as Deterministic Code, Closed-Loop AI, Assisted AI, or Human Only. The cheapest option that meets the constraints wins. Layer 3 applies only to the Closed-Loop AI parts and lists five rules: Bounded, Grounded, Gated, Observed, and Governed. If any rule fails, that piece runs as Assisted AI instead, with a human in the loop. The repository itself is mostly documents. The main artifact is a 34 page PDF spec with a 57 item checklist that builders can walk through to grade a workflow. There are two infographic PNGs that explain the ideas visually, and a sample HTML report you can open in a browser to see what the output looks like. The repo also ships a companion tool called AgentTwin. It is a skill you drop into an AI assistant such as Claude Code. You point it at an agent, automation, or vendor pitch, and it walks the 57 item rubric and produces a two view HTML report: a plain English summary with a letter grade for executives, and a detailed process map view for builders. Install steps and a test prompt are included in the README.

Copy-paste prompts

Prompt 1
Walk me through the AAC three-layer framework using my customer support workflow as the example, and assign a runtime tag to each step.
Prompt 2
Install the AgentTwin skill in Claude Code and run it against this vendor pitch, then produce the two-view HTML report described in the README.
Prompt 3
Score my proposed AI agent against the 57-item AAC checklist and tell me which of Bounded, Grounded, Gated, Observed, Governed it fails.
Prompt 4
Take my process map and identify which nodes should run as Closed-Loop AI versus Assisted AI based on the AAC rules.
Prompt 5
Write a one-page executive summary of why an AI project failed, framed using the AAC argument that runtime was chosen before the process was mapped.
Open on GitHub → Explain another repo

Generated 2026-05-22 · Model: sonnet-4-6 · Verify against the repo before relying on details.