← ClaudeAtlas

create-flowlisted

Plans the Power Automate flows a system needs with the user in a flow.md (how many flows, what triggers each, what each does), then builds one .zip per approved flow for import with My flows > Import > Import Package (Legacy), with the connections to pick and a post-import checklist. Use when someone wants to "automate this process", asks which flows they need, wants a Power Automate flow, a notification or an approval, or an import package, brings a package that failed to import, or has run-flow actions in a mock-ui mockup. Does not create lists or screens: that is create-list and create-app.
YKUNAKORN/Supuersub · ★ 0 · AI & Automation · score 62
Install: claude install-skill YKUNAKORN/Supuersub
# Power Automate flows: plan in flow.md, then build legacy import packages Produce `flow.md` (the plan the user approves), then per approved flow a spec `<FlowName>.flow.json` and `<FlowName>_LegacyPackage.zip`. Reply in the user's language; display names and `flow.md` follow it, identifiers stay ASCII. Paths are relative to this skill's folder: `${CLAUDE_SKILL_DIR}`, or run from that folder. **This is the riskiest skill in the plugin.** A slightly wrong package fails on import with an unhelpful message. Only the owner's reference flow (button trigger, Compose, Send an email (V2)) has been import-tested. Work from the catalog, label everything else, and never present a guess as a fact. ## The workflow (in order) 1. **Listen, then ask.** Restate the system as you understand it. Ask about triggers (button, Power Apps, schedule, list event), who is notified, approvals, documents, schedules, failure cases and volumes, in at most two rounds. Use `supersub/mockup/sitemap.json` when it exists (its `run-flow:<Name>` actions name the flows and the screen and control that call them) and `supersub/lists/*.list.json` (list and column internal names). Never assume either exists. 2. **Write `flow.md` and stop.** Follow [`references/flow-md-template.md`](references/flow-md-template.md): the system in brief with assumptions and open questions, the inventory table with a status per flow (`package`, `package with unverified steps`, `build by hand`), each flow in ful