/uipath-genome

name: uipath-genome
description: "UiPath automation genome (`*-genome.md`): always invoke to build, execute or edit a genome file, before any skill it names. Portable markdown blueprint of an automation at process and component level: steps, business rules, handoffs, platform resources, acceptance criteria, and the UiPath skill that builds each part. EXTRACT a genome from a UiPath project or solution (`.xaml`/`.cs`, `.flow`, `.bpmn`, `agent.json`, `Workflow.json`, `caseplan.case`/`.json`, `.uipx`) or another automation or test framework's export, for documentation, a refactor or migration to UiPath; AUTHOR one from an idea; EXECUTE one to build it. Triggers: 'genome', 'blueprint', 'document this automation/solution/process', 'reverse-engineer this project', 'build/implement this genome'. PDD/SDD, SOP or idea to design without a genome→uipath-planner. Build without a genome→that artifact's skill. Legacy activity upgrade→uipath-activity-migrator. Quality review→uipath-review."
when_to_use: "User points at a *-genome.md file (or one whose first line is `<!-- UIPATH-AUTOMATION-GENOME`) and asks to build, execute, implement, follow or edit it. User says 'genome', 'blueprint', 'document what this automation does', 'extract a spec from this project/solution', 'reverse-engineer this process', 'describe this solution at high and low level', 'propose a workshop or demo scenario to build'. User asks to refactor a UiPath automation ('refactor this process', 'rebuild it on Maestro or Portable')."

UiPath Genome — document, author, and execute automation blueprints

Genome: markdown specification an AI agent consumes to rebuild an automation — what it does, business rules, data moving between parts, platform resources, its transactional shape, verification, and which UiPath skill builds each part. Genomes stay thin: build skills carry UiPath know-how; a genome describes *what*, skills know *how*.

> **Read by the mode's read plan (§ Read Plans), never from memory.** This file routes; guides carry the rules, each subject in exactly one guide. A file the plan reads whole is read whole — not grepped or skimmed; a pointer that names a section (`guide.md § Section`) is a section read, that section in full; a guide no condition of the plan has reached stays closed, and the `CLAUDE.md` beside this file, which governs editing the skill, is not read in a run. A framework selectors guide's per-technology tables are a **catalog**, read by section: list its headings, then read the sections for the technologies the source recorded; the rules around them are read whole.

When to Use This Skill

• Existing UiPath project or solution to document, understand, or prepare for migration ("what does this solution do", "extract a genome", "document this process at high and low level")
• Existing UiPath automation to refactor: rebuilt on another UiPath product, framework or architecture, its behaviour kept; or another framework's automation migrated with a refactor, when asked
• Described automation idea needing a specification before building, or a goal (a self-paced workshop, a demo, trying a product) needing a scenario proposed first
• `*-genome.md` file to build from
• Existing genome to update, split into components, or re-extract after source changed

Mode Detection

Determine mode from input, in this order:

1. **`*-genome.md` path plus build intent** ("build", "execute", "implement", "follow") → **Execute**. Read [execution-guide.md](references/execution-guide.md). 2. **A UiPath project or solution, or another framework's export, plus refactor intent** ("refactor", "re-platform", "rebuild it on Maestro, API workflows or Portable", "move it off the Windows robot", "migrate and modernize it") → **Extract** its genome first; once it is written and the user's edits are in (an unattended run goes straight on), **Execute** that genome: executing a genome extracted from a UiPath source is a refactor, and so is executing one from another framework when the request asks for a refactor ([refactor-guide.md](references/refactor-guide.md)). An upgrade of a Windows-Legacy project's activities in place stays `uipath-activity-migrator`'s. 3. **Directory, project file, solution manifest, or another framework's export** (`project.json`, `project.uiproj`, `.uipx`, `.flow`, `.bpmn`, `agent.json`, `Workflow.json`, `caseplan.case`, `caseplan.json`, `uipath.json`; or a folder with none of these holding another automation or test framework's export) → **Extract**. Read [extraction-guide.md](references/extraction-guide.md) and the framework's guides (§ Source Frameworks). A `.bpmn` here is an existing process project to document; a BPMN model handed over as the design to build from is `uipath-planner`'s. A Windows-Legacy UiPath project whose activities are to be upgraded in place is `uipath-activity-migrator`'s; documenting it, or blueprinting it for a rebuild, is an extraction. 4. **Description, idea, SOP, transcript or other process document with no source project, when the user asks for a genome or blueprint; or a goal to propose a scenario for** (a self-paced workshop, a demo, trying a product) → **Author**. Read [authoring-guide.md](references/authoring-guide.md). The same input without a genome or blueprint asked for — designing or building from an SOP, a transcript, a process spec or an idea — is `uipath-planner`'s. 5. **`*-genome.md` path plus edit intent** ("update", "add a step", "split", "remove the inferred flags") → **Edit**. Read [editing-guide.md](references/editing-guide.md): its edit table, and — when the source changed or the extraction was cut short — its § Partial Re-extraction, which re-extracts only the changed or unread objects.

A PDD or SDD with no genome or blueprint asked for, a request to design a solution and derive tasks, or any input this list assigns to another skill is that skill's job, not a genome. Say so and stop.

Read Plans

Every turn resends the whole context: a reference read early