diff --git a/skills/uipath-automation-discovery/SKILL.md b/skills/uipath-automation-discovery/SKILL.md index 4e5a94134b..1d2e97c7a2 100644 --- a/skills/uipath-automation-discovery/SKILL.md +++ b/skills/uipath-automation-discovery/SKILL.md @@ -1,6 +1,6 @@ --- name: uipath-automation-discovery -description: "UiPath automation discovery — mines Slack/email/wikis/CRM/HRIS/ERP for repetitive work, SPOFs, and replicable models; produces a 4-tier prioritized opportunity report with UiPath implementation paths. Use to discover automation opportunities, find what to automate, or run an internal automation audit across an organization. For building a specific automation→uipath-rpa, authoring a Flow→uipath-maestro-flow, working with agents→uipath-agents." +description: "UiPath automation discovery — mines Slack/email/wikis/CRM/HRIS/ERP for repetitive work, SPOFs, and replicable models; produces a 4-tier prioritized opportunity report with UiPath implementation paths, then sizes build effort (complexity band → pack-hours → contingency). Use to discover automation opportunities, find what to automate, estimate/size a delivery, or run an internal automation audit across an organization. For building a specific automation→uipath-rpa, authoring a Flow→uipath-maestro-flow, working with agents→uipath-agents." --- # Automation Discovery @@ -15,6 +15,7 @@ UiPath-ready backlog with recommended implementation paths. - User wants to **find manual work to automate** and build a UiPath implementation backlog - User asks "what should we automate?" while working with UiPath tools - User wants an **internal automation audit** to feed into UiPath Automation Hub or a UiPath pipeline +- User asks to **estimate / size / cost** discovered opportunities — pack-hours, delivery effort, complexity bands, contingency - User explicitly invokes `/uipath-automation-discovery` ## Critical Rules @@ -24,6 +25,7 @@ UiPath-ready backlog with recommended implementation paths. 3. **Verify access before mining.** Test each data source with a minimal read-only operation. If access fails, note it and move on — don't block discovery. 4. **Evidence over opinion.** Every opportunity (Tiers 1-3) must cite a specific source, quantitative metric, and affected role or team. No unsupported claims. If a source yields fewer than 5 signals, mark all findings from that source as low-confidence. Do not promote low-confidence findings above Tier 3, except per Rule 5. 5. **Replication is always Tier 1.** A proven model backed by a working automation that could replicate elsewhere is the highest-value finding — this overrides Rule 4's Tier 3 cap. If the replicable model's source has fewer than 5 signals, classify as Tier 1 with a low-confidence flag until corroborated by a second source. Always lead with replicable models. Never skip the replicable-model search (Phase 2C). +6. **Never invent pack-hours or complexity thresholds (Phase 4.5).** When estimating build effort, the band→hours numbers and matrix thresholds come from the user-supplied Core RPA / Agentic complexity matrices and Pack-Hours catalogue. Do NOT recall or fabricate them — if they are not supplied, STOP and ask. Adjustment-factor and contingency percentages are `[CALIBRATE]` defaults the user confirms against actuals. Fabricated numbers recreate the estimation error this phase exists to prevent. ## Workflow Overview @@ -33,6 +35,7 @@ Phase 1: MINE → Gather raw data from all verified sources Phase 2: ANALYZE → Extract patterns, SPOFs, replicable models, gaps Phase 3: REFLECT → Layer on business strategy for strategic gaps Phase 4: REPORT → Produce prioritized report with 4 tiers +Phase 4.5: ESTIMATE→ Size build effort (band → pack-hours → contingency) — on request Phase 5: HANDOFF → Map opportunities to UiPath implementation skills ``` @@ -189,6 +192,25 @@ tier definitions, evidence standards, and platform-specific guidance. - ROI benchmarks from existing projects included - Strategic analysis ties to real financials +## Phase 4.5: ESTIMATE (optional — on request) + +Run only when the user wants build-effort sizing (pack-hours, delivery +estimate, complexity bands, contingency). Sizes each prioritized opportunity: +opportunity → complexity band → pack-hours → adjustment factors → contingency → +total. This is delivery/pre-sales sizing — distinct from the ROI/hours-saved +impact already in the report. + +The band→hours numbers and matrix thresholds are **authoritative references the +user supplies** (Core RPA + Agentic complexity matrices, Pack-Hours catalogue) — +never invented (Critical Rule 6). Ask for them if absent. The method adds the +pieces that were missing: an above-ceiling/decompose rule (>7 apps / >8 +variations), a multi-entity redeploy factor, an existing-automation rebuild +discount, confidence-tiered contingency, and one unified band→hours mapping that +resolves the Tool vs Process-Automation grain. + +See [references/estimation-guide.md](references/estimation-guide.md) and +[assets/templates/estimation-worksheet-template.md](assets/templates/estimation-worksheet-template.md). + ## Phase 5: HANDOFF Map each Tier 1-2 opportunity to a UiPath implementation path. Add a @@ -223,6 +245,7 @@ each phase with a brief summary and ask if the user wants to adjust scope. - [references/intake-guide.md](references/intake-guide.md) — Phase 0 detailed steps (company context, tool inventory, access verification, privacy) - [references/mining-guide.md](references/mining-guide.md) — Per-source search guidance (load during Phase 1) - [references/report-template.md](references/report-template.md) — Output structure, tier definitions, and evidence standards (load during Phase 4) +- [references/estimation-guide.md](references/estimation-guide.md) — Estimation accelerator: opportunity → band → pack-hours → contingency (load during Phase 4.5, on request) ## Anti-patterns @@ -232,3 +255,5 @@ each phase with a brief summary and ask if the user wants to adjust scope. - **Promising ROI without source citations.** Every ROI estimate must reference an existing project benchmark or explicit data point. - **Skipping the replicable-model search.** The highest-value findings are always proven models that can replicate. Never skip Phase 2C. - **Speculating from insufficient evidence.** Below signal threshold → mark low confidence. Insufficient evidence → don't promote to Tier 1-3. +- **Fabricating pack-hours or matrix thresholds (Phase 4.5).** The band→hours numbers are authoritative user-supplied references. Guessing them recreates the estimation error the accelerator exists to prevent — stop and ask for the catalogue and matrices. +- **Clamping oversized opportunities at "High".** A cluster over the matrix ceiling (>7 apps / >8 variations) must be decomposed and summed, not sized as a single "High" unit — this was the largest source of under-estimation. diff --git a/skills/uipath-automation-discovery/assets/templates/estimation-worksheet-template.md b/skills/uipath-automation-discovery/assets/templates/estimation-worksheet-template.md new file mode 100644 index 0000000000..53fb6423a8 --- /dev/null +++ b/skills/uipath-automation-discovery/assets/templates/estimation-worksheet-template.md @@ -0,0 +1,80 @@ +# Estimation Worksheet — + +Generated by: uipath-automation-discovery + +> **Numbers below marked `[FROM CATALOGUE]` come from the user-supplied +> Pack-Hours catalogue and complexity matrices — never invented.** Values marked +> `[CALIBRATE]` are default assumptions to confirm against actuals before the +> estimate is treated as final. See +> [references/estimation-guide.md](../../references/estimation-guide.md). + +## 1. Sources + +| Artifact | Provided? | Reference / path | +|---|---|---| +| Opportunity register | | | +| Core RPA complexity matrix | | | +| Agentic complexity matrix | | | +| Pack-Hours catalogue | | | +| Benchmark (Delivery Summary) | | | + +## 2. Unified band→hours mapping + +Filled from the Pack-Hours catalogue. One row per band × grain. + +| Complexity band | Grain | Core RPA hours | Agentic add-on hours | Catalogue source | +|---|---|---|---|---| +| Simple | Process-Automation | `[FROM CATALOGUE]` | `[FROM CATALOGUE]` | | +| Simple | Tool | `[FROM CATALOGUE]` | — | | +| Medium | Process-Automation | `[FROM CATALOGUE]` | `[FROM CATALOGUE]` | | +| Medium | Tool | `[FROM CATALOGUE]` | — | | +| High | Process-Automation | `[FROM CATALOGUE]` | `[FROM CATALOGUE]` | | +| High | Tool | `[FROM CATALOGUE]` | — | | + +## 3. Per-opportunity estimate + +| # | Opportunity | Grain | Band | Base hours (source) | Redeploy factor | Rebuild discount | Confidence | Contingency % | Total hours | +|---|---|---|---|---|---|---|---|---|---| +| 1 | | | | (`[FROM CATALOGUE]`) | <×N entities> | <−%> | | `[CALIBRATE]` | | +| 2 | | | | | | | | | | + +Show the math per row: `total = (base ± factors) × (1 + contingency)`. + +## 4. Above-ceiling decomposition log + +For any opportunity > 7 apps or > 8 variations, decomposed and summed. + +| Parent opportunity | Trigger (apps / variations) | Sub-unit | Grain | Band | Hours | +|---|---|---|---|---|---| +| | | | | | | +| | | | | | | +| | | **Parent subtotal** | | | | + +## 5. Calibration register + +Every assumption the user must confirm before the estimate is final. + +| Assumption | Default used | Confirmed value | Basis | +|---|---|---|---| +| Multi-entity redeploy increment | `[CALIBRATE ~15-30%]` per extra entity | | | +| Existing-automation rebuild discount | `[CALIBRATE ~20-40%]` | | | +| Contingency — High confidence | `[CALIBRATE ~10-15%]` | | | +| Contingency — Medium confidence | `[CALIBRATE ~20-30%]` | | | +| Contingency — Low confidence | `[CALIBRATE ~40%+]` | | | + +## 6. Scenario roll-up + +| Scenario | Assumptions | Portfolio total (h) | +|---|---|---| +| Option 1 — conservative full-build | no decomposition reuse, high contingency | | +| Option 2 — decomposition + reuse + redeploy | rebuild discount + redeploy factor applied | | + +## 7. Benchmark reconciliation (if a benchmark exists) + +| Line | Hours | +|---|---| +| This worksheet (chosen scenario) | | +| Benchmark (Delivery Summary) | | +| **Delta** | | + +**Delta drivers:** diff --git a/skills/uipath-automation-discovery/references/estimation-guide.md b/skills/uipath-automation-discovery/references/estimation-guide.md new file mode 100644 index 0000000000..0f7bd31ae2 --- /dev/null +++ b/skills/uipath-automation-discovery/references/estimation-guide.md @@ -0,0 +1,104 @@ +# Estimation Accelerator + +Size the **build effort** of a prioritized opportunity register: opportunity → +complexity band → pack-hours → adjustment factors → contingency → total. Runs +after Phase 4 (the report already carries the register + per-opportunity +confidence). This is delivery/pre-sales sizing, not the ROI/hours-saved impact +in the report. + +Load when the user asks to estimate, size, cost, or produce pack-hours / +effort / a delivery estimate for discovered opportunities. + +## Hard rule — never invent pack-hours + +The band→hours numbers and the complexity-matrix thresholds are **authoritative +UiPath references the user supplies** — the Core RPA complexity matrix, the +Agentic complexity matrix, and the Pack-Hours catalogue. Do NOT recall, +approximate, or fabricate them. Unverified numbers are the exact failure this +accelerator exists to prevent. + +1. If the user has not supplied the Pack-Hours catalogue and the complexity + matrices, STOP and ask for them (file paths or pasted tables). Do not + proceed with guessed hours. +2. Every band→hours value written to the worksheet cites its catalogue source. +3. Adjustment-factor and contingency percentages below are **not** authoritative + — they are `[CALIBRATE]` defaults the user tunes against the org's actuals + before the estimate is final. +4. Show the math for every opportunity (base → factors → contingency → total) + so each number is auditable. + +## Inputs + +| Input | Source | Notes | +|---|---|---| +| Opportunity register | Phase 4 report, or user `.xlsx` | Per opportunity: apps touched, variations / decision points, data & exception complexity, agentic vs deterministic, rebuild-of-existing?, deploy entity count | +| Core RPA complexity matrix | **User-supplied** | Band thresholds (apps, variations, data, exceptions) | +| Agentic complexity matrix | **User-supplied** | Band thresholds for reasoning steps, tools, autonomy, HITL | +| Pack-Hours catalogue | **User-supplied** | Band × grain → hours | +| Benchmark (optional) | Delivery Summary / official estimate | For reconciliation | + +## Procedure — per opportunity + +1. **Determine grain.** Is the unit a **Process-Automation** (end-to-end + process) or a **Tool** (reusable component / pack invoked by processes)? + Price at the matching grain — a decomposed sub-unit is often Tool-grain. + Grain ambiguity was a root cause of the estimate divergence; resolve it + explicitly and record it. +2. **Classify complexity** on the matrix dimensions: deterministic RPA work → + Core RPA matrix; agentic/reasoning components → Agentic matrix. A hybrid + opportunity carries both a Core RPA band and an Agentic add-on. +3. **Assign band** (Simple / Medium / High) from the matrix — unless the + above-ceiling rule fires. +4. **Above-ceiling / decompose rule.** If an opportunity exceeds the matrix + ceiling — **> 7 applications OR > 8 variations / decision points** — do NOT + clamp it to "High". Decompose into sub-automations (by sub-process or + application cluster), classify and size each at its own grain, and sum. + Record the decomposition. Clamping oversized clusters at "High" is the + single largest source of under-estimation — this rule is the primary fix. +5. **Map band → base pack-hours** from the supplied catalogue at the resolved + grain. Cite the catalogue row. +6. **Apply adjustment factors** (`[CALIBRATE]` defaults — confirm against + actuals): + - **Multi-entity redeploy:** same automation deployed across N legal + entities / regions → do NOT count each as a full build. `base + (N-1) × + [CALIBRATE ~15-30%] × base` per additional entity; raise it when per-entity + localization or regulatory variation is significant. + - **Existing-automation rebuild discount:** rebuilding / migrating an + automation that already exists (known logic, documented process) → + `[CALIBRATE ~20-40%]` reduction vs greenfield, scaled by reuse and + documentation quality. +7. **Add confidence-tiered contingency**, keyed to the opportunity's discovery + confidence: High `[CALIBRATE ~10-15%]`, Medium `[~20-30%]`, Low / ambiguous + scope / unknown systems `[~40%+]`. +8. **Total** = (base ± factors) × (1 + contingency). Write base, each factor, + contingency, and total to the worksheet. + +## Unified band→hours mapping (ask #3) + +Replace the disconnected matrix-image + catalogue pair with one table so band, +grain, and hours live together. Fill values from the user's catalogue: + +| Complexity band | Grain | Core RPA hours | Agentic add-on hours | Catalogue source | +|---|---|---|---|---| +| Simple | Process-Automation | `[FROM CATALOGUE]` | `[FROM CATALOGUE]` | `` | +| Simple | Tool | `[FROM CATALOGUE]` | — | `` | +| Medium | … | … | … | … | +| High | … | … | … | … | +| Above-ceiling | (decompose) | sum of sub-units | sum of sub-units | — | + +## Scenarios & reconciliation + +- Produce ≥ 2 scenarios (e.g. **Option 1** conservative full-build; **Option 2** + with decomposition + rebuild discount + redeploy factor applied). The source + engagement delivered three (16.2k / 12.1k / 10.7k h) — the spread comes from + these factors, not from different base numbers. +- When a benchmark estimate exists, reconcile the portfolio total against it and + attribute each material delta to a band, factor, or decomposition decision. + +## Output + +Use [assets/templates/estimation-worksheet-template.md](../assets/templates/estimation-worksheet-template.md): +per-opportunity estimate table, the unified band→hours mapping, the +decomposition log, the calibration register (every `[CALIBRATE]` value awaiting +confirmation), and the scenario roll-up. Append an **Estimation** section to the +Phase 4 report, or emit a standalone worksheet.