@uipath/delegate-sdk 1.203.1 → 1.203.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +41 -3
- package/dist/index.mjs +2 -2
- package/dist/skills/business-analysis/SKILL.md +722 -0
- package/dist/skills/business-analysis/as-is-capture.md +440 -0
- package/dist/skills/business-analysis/assets/progress.yaml +19 -0
- package/dist/skills/business-analysis/assets/task-list.md +34 -0
- package/dist/skills/business-analysis/automation-hub-publishing.md +47 -0
- package/dist/skills/business-analysis/bpmn-to-be-design.md +274 -0
- package/dist/skills/business-analysis/case-to-be-design.md +223 -0
- package/dist/skills/business-analysis/diagram-authoring.md +215 -0
- package/dist/skills/business-analysis/industry-gaps.md +134 -0
- package/dist/skills/business-analysis/interview-spine.md +297 -0
- package/dist/skills/business-analysis/locales/de.json +54 -0
- package/dist/skills/business-analysis/locales/en.json +54 -0
- package/dist/skills/business-analysis/locales/es-MX.json +54 -0
- package/dist/skills/business-analysis/locales/es.json +54 -0
- package/dist/skills/business-analysis/locales/fr.json +54 -0
- package/dist/skills/business-analysis/locales/ja.json +54 -0
- package/dist/skills/business-analysis/locales/ko.json +54 -0
- package/dist/skills/business-analysis/locales/pt-BR.json +54 -0
- package/dist/skills/business-analysis/locales/pt.json +54 -0
- package/dist/skills/business-analysis/locales/ro.json +54 -0
- package/dist/skills/business-analysis/locales/tr.json +54 -0
- package/dist/skills/business-analysis/locales/zh-CN.json +54 -0
- package/dist/skills/business-analysis/locales/zh-TW.json +54 -0
- package/dist/skills/business-analysis/pdd-generation.md +204 -0
- package/dist/skills/business-analysis/pdd-template.md +562 -0
- package/dist/skills/business-analysis/progress-presentation.json +13 -0
- package/dist/skills/business-analysis/recording-first.md +19 -0
- package/dist/skills/business-analysis/recording-processing.md +152 -0
- package/dist/skills/business-analysis/references/automation-hub-open-api.md +57 -0
- package/dist/skills/business-analysis/references/case-definition-spec.md +90 -0
- package/dist/skills/business-analysis/references/case-design-patterns/loan-origination-spec.md +86 -0
- package/dist/skills/business-analysis/references/component-type-mapping.md +52 -0
- package/dist/skills/business-analysis/references/uipath-products/case-management-schema.md +62 -0
- package/dist/skills/business-analysis/references/uipath-products/maestro-case-framework.md +65 -0
- package/dist/skills/business-analysis/references/uipath-products/maestro-case-management.md +49 -0
- package/dist/skills/business-analysis/research-offer.md +104 -0
- package/dist/skills/business-analysis/research-pass.md +149 -0
- package/dist/skills/business-analysis/scripts/assemble-pdd.ps1 +294 -0
- package/dist/skills/business-analysis/scripts/assemble-pdd.sh +453 -0
- package/dist/skills/business-analysis/scripts/check-phase-ready.ps1 +72 -0
- package/dist/skills/business-analysis/scripts/check-phase-ready.sh +98 -0
- package/dist/skills/business-analysis/scripts/lint-diagram.ps1 +524 -0
- package/dist/skills/business-analysis/scripts/lint-diagram.sh +519 -0
- package/dist/skills/business-analysis/scripts/stamp-pages.ps1 +363 -0
- package/dist/skills/business-analysis/scripts/stamp-pages.sh +360 -0
- package/dist/skills/business-analysis/to-be-design.md +199 -0
- package/dist/skills/confluence/SKILL.md +386 -0
- package/dist/skills/doc-coauthoring/SKILL.md +295 -0
- package/dist/skills/excel-architect/SKILL.macos.md +161 -0
- package/dist/skills/excel-architect/SKILL.md +180 -0
- package/dist/skills/excel-architect/SKILL.windows.md +61 -0
- package/dist/skills/excel-architect/archetypes/01-financial-model-advanced.md +332 -0
- package/dist/skills/excel-architect/archetypes/01-financial-model.md +248 -0
- package/dist/skills/excel-architect/archetypes/02-data-analysis.md +171 -0
- package/dist/skills/excel-architect/archetypes/03-tracking-dashboard.md +160 -0
- package/dist/skills/excel-architect/archetypes/04-project-planning.md +193 -0
- package/dist/skills/excel-architect/archetypes/05-simple-table.md +111 -0
- package/dist/skills/excel-architect/building.md +279 -0
- package/dist/skills/excel-architect/create.md +64 -0
- package/dist/skills/excel-architect/data-and-formulas.md +186 -0
- package/dist/skills/excel-architect/generator.md +272 -0
- package/dist/skills/excel-architect/macos/scripts/add-data-validation.applescript +242 -0
- package/dist/skills/excel-architect/macos/scripts/append-rows.applescript +310 -0
- package/dist/skills/excel-architect/macos/scripts/apply-conditional-format.applescript +565 -0
- package/dist/skills/excel-architect/macos/scripts/autofit-columns.applescript +79 -0
- package/dist/skills/excel-architect/macos/scripts/benchmark.sh +135 -0
- package/dist/skills/excel-architect/macos/scripts/check-compile.sh +30 -0
- package/dist/skills/excel-architect/macos/scripts/clear-range.applescript +152 -0
- package/dist/skills/excel-architect/macos/scripts/copy-paste.applescript +179 -0
- package/dist/skills/excel-architect/macos/scripts/create-chart.applescript +531 -0
- package/dist/skills/excel-architect/macos/scripts/create-pivot.applescript +443 -0
- package/dist/skills/excel-architect/macos/scripts/create-sheets.applescript +264 -0
- package/dist/skills/excel-architect/macos/scripts/create-workbook.applescript +92 -0
- package/dist/skills/excel-architect/macos/scripts/delete-chart.applescript +105 -0
- package/dist/skills/excel-architect/macos/scripts/delete-sheet.applescript +127 -0
- package/dist/skills/excel-architect/macos/scripts/filter-data.applescript +213 -0
- package/dist/skills/excel-architect/macos/scripts/find-replace.applescript +238 -0
- package/dist/skills/excel-architect/macos/scripts/format-range.applescript +531 -0
- package/dist/skills/excel-architect/macos/scripts/freeze-panes.applescript +133 -0
- package/dist/skills/excel-architect/macos/scripts/get-current-file.applescript +24 -0
- package/dist/skills/excel-architect/macos/scripts/get-sheet-dimensions.applescript +115 -0
- package/dist/skills/excel-architect/macos/scripts/health-check.applescript +704 -0
- package/dist/skills/excel-architect/macos/scripts/list-open-workbooks.applescript +80 -0
- package/dist/skills/excel-architect/macos/scripts/maximize-window.applescript +47 -0
- package/dist/skills/excel-architect/macos/scripts/merge-cells.applescript +227 -0
- package/dist/skills/excel-architect/macos/scripts/open-workbook.applescript +139 -0
- package/dist/skills/excel-architect/macos/scripts/read-range.applescript +267 -0
- package/dist/skills/excel-architect/macos/scripts/rename-sheet.applescript +231 -0
- package/dist/skills/excel-architect/macos/scripts/select-sheet.applescript +133 -0
- package/dist/skills/excel-architect/macos/scripts/set-tab-color.applescript +109 -0
- package/dist/skills/excel-architect/macos/scripts/sort-data.applescript +136 -0
- package/dist/skills/excel-architect/macos/scripts/undo.applescript +59 -0
- package/dist/skills/excel-architect/macos/scripts/workbook-lifecycle.applescript +149 -0
- package/dist/skills/excel-architect/macos/scripts/write-formula.applescript +225 -0
- package/dist/skills/excel-architect/macos/scripts/write-range.applescript +351 -0
- package/dist/skills/excel-architect/reference/api/advanced.md +381 -0
- package/dist/skills/excel-architect/reference/api/basic.md +747 -0
- package/dist/skills/excel-architect/reference/guides.md +348 -0
- package/dist/skills/excel-architect/reference/repair.md +174 -0
- package/dist/skills/excel-architect/reference/troubleshooting.md +46 -0
- package/dist/skills/excel-architect/scripting.md +266 -0
- package/dist/skills/excel-architect/styling-and-features.md +433 -0
- package/dist/skills/excel-architect/windows/api/composites.md +337 -0
- package/dist/skills/excel-architect/windows/api/scripting.md +139 -0
- package/dist/skills/excel-architect/windows/examples/level-1-workflows.md +485 -0
- package/dist/skills/excel-architect/windows/examples/level-2-advanced.md +690 -0
- package/dist/skills/excel-architect/windows/examples/level-3-scripting.md +337 -0
- package/dist/skills/github/SKILL.md +446 -0
- package/dist/skills/github/recipes/add-comment.md +85 -0
- package/dist/skills/github/recipes/check-pr-status.md +122 -0
- package/dist/skills/github/recipes/compare-branches.md +79 -0
- package/dist/skills/github/recipes/create-issue.md +103 -0
- package/dist/skills/github/recipes/create-pr.md +97 -0
- package/dist/skills/github/recipes/get-file-contents.md +76 -0
- package/dist/skills/github/recipes/get-last-commit.md +128 -0
- package/dist/skills/github/recipes/list-my-open-prs.md +105 -0
- package/dist/skills/github/recipes/list-recent-commits.md +84 -0
- package/dist/skills/github/recipes/search-issues.md +115 -0
- package/dist/skills/google-workspace/SKILL.md +217 -0
- package/dist/skills/google-workspace/services/calendar.md +311 -0
- package/dist/skills/google-workspace/services/docs.md +426 -0
- package/dist/skills/google-workspace/services/drive.md +504 -0
- package/dist/skills/google-workspace/services/gmail.md +466 -0
- package/dist/skills/google-workspace/services/sheets.md +370 -0
- package/dist/skills/internal-comms/SKILL.md +35 -0
- package/dist/skills/internal-comms/examples/3p-updates.md +47 -0
- package/dist/skills/internal-comms/examples/company-newsletter.md +65 -0
- package/dist/skills/internal-comms/examples/faq-answers.md +30 -0
- package/dist/skills/internal-comms/examples/general-comms.md +15 -0
- package/dist/skills/jira/SKILL.md +397 -0
- package/dist/skills/jira/recipes/add-comment.md +123 -0
- package/dist/skills/jira/recipes/assign-issue.md +157 -0
- package/dist/skills/jira/recipes/create-issue.md +274 -0
- package/dist/skills/jira/recipes/get-issue-details.md +154 -0
- package/dist/skills/jira/recipes/list-projects.md +151 -0
- package/dist/skills/jira/recipes/my-issues.md +180 -0
- package/dist/skills/jira/recipes/search-issues.md +215 -0
- package/dist/skills/jira/recipes/transition-issue.md +154 -0
- package/dist/skills/jira/recipes/troubleshooting.md +387 -0
- package/dist/skills/knowledge-base/SKILL.md +289 -0
- package/dist/skills/media-tools/SKILL.md +204 -0
- package/dist/skills/media-tools/references/encode-runbook.md +24 -0
- package/dist/skills/media-tools/references/resolve-binaries.md +81 -0
- package/dist/skills/media-tools/scripts/macos/ff-launch.sh +22 -0
- package/dist/skills/media-tools/scripts/macos/ff-poll.sh +10 -0
- package/dist/skills/media-tools/scripts/windows/ff-launch.ps1 +34 -0
- package/dist/skills/media-tools/scripts/windows/ff-poll.ps1 +20 -0
- package/dist/skills/office-download/SKILL.md +161 -0
- package/dist/skills/outlook-365/SKILL.macos.md +331 -0
- package/dist/skills/outlook-365/SKILL.md +171 -0
- package/dist/skills/outlook-365/SKILL.windows.md +124 -0
- package/dist/skills/outlook-365/api/bulk-email-operations.md +178 -0
- package/dist/skills/outlook-365/api/check-availability.md +87 -0
- package/dist/skills/outlook-365/api/create-inbox-rule.md +182 -0
- package/dist/skills/outlook-365/api/download-attachments.md +149 -0
- package/dist/skills/outlook-365/api/find-and-email-contact.md +185 -0
- package/dist/skills/outlook-365/api/manage-calendar-events.md +189 -0
- package/dist/skills/outlook-365/api/organize-with-folders.md +178 -0
- package/dist/skills/outlook-365/api/reply-to-conversation.md +68 -0
- package/dist/skills/outlook-365/api/schedule-meeting.md +73 -0
- package/dist/skills/outlook-365/api/search-and-read-email.md +93 -0
- package/dist/skills/outlook-365/api/send-email-with-attachments.md +94 -0
- package/dist/skills/outlook-365/api/send-email.md +396 -0
- package/dist/skills/outlook-365/api/set-out-of-office.md +196 -0
- package/dist/skills/outlook-365/macos/scripts/bulk-operations.applescript +429 -0
- package/dist/skills/outlook-365/macos/scripts/calendar.applescript +642 -0
- package/dist/skills/outlook-365/macos/scripts/contacts.applescript +635 -0
- package/dist/skills/outlook-365/macos/scripts/helpers.applescript +227 -0
- package/dist/skills/outlook-365/macos/scripts/read-emails.applescript +299 -0
- package/dist/skills/outlook-365/macos/scripts/search-emails.applescript +339 -0
- package/dist/skills/outlook-365/macos/scripts/send-email.applescript +245 -0
- package/dist/skills/outlook-365/uia/BASIC_OPERATIONS.md +278 -0
- package/dist/skills/outlook-365/uia/CALENDAR_OPERATIONS.md +386 -0
- package/dist/skills/outlook-365/uia/COMPOSE_EMAIL.md +426 -0
- package/dist/skills/outlook-365/uia/README.md +75 -0
- package/dist/skills/outlook-365/windows/com/bulk-operations.ps1 +241 -0
- package/dist/skills/outlook-365/windows/com/calendar.ps1 +227 -0
- package/dist/skills/outlook-365/windows/com/contacts.ps1 +270 -0
- package/dist/skills/outlook-365/windows/com/helpers.ps1 +158 -0
- package/dist/skills/outlook-365/windows/com/read-emails.ps1 +115 -0
- package/dist/skills/outlook-365/windows/com/search-emails.ps1 +141 -0
- package/dist/skills/outlook-365/windows/com/send-email.ps1 +121 -0
- package/dist/skills/pdf-architect/SKILL.md +640 -0
- package/dist/skills/powerpoint-architect/SKILL.macos.md +271 -0
- package/dist/skills/powerpoint-architect/SKILL.md +853 -0
- package/dist/skills/powerpoint-architect/SKILL.windows.md +458 -0
- package/dist/skills/powerpoint-architect/custom_themes.md +141 -0
- package/dist/skills/powerpoint-architect/editing-guide.md +424 -0
- package/dist/skills/powerpoint-architect/generator-reference.md +668 -0
- package/dist/skills/powerpoint-architect/images-guide.md +207 -0
- package/dist/skills/powerpoint-architect/issue-fix-mapping.md +768 -0
- package/dist/skills/powerpoint-architect/macos/scripts/add-html-to-slide.applescript +389 -0
- package/dist/skills/powerpoint-architect/macos/scripts/add-slide.applescript +255 -0
- package/dist/skills/powerpoint-architect/macos/scripts/add-speaker-notes.applescript +132 -0
- package/dist/skills/powerpoint-architect/macos/scripts/add-text.applescript +245 -0
- package/dist/skills/powerpoint-architect/macos/scripts/apply-slide-layout.applescript +80 -0
- package/dist/skills/powerpoint-architect/macos/scripts/apply-theme.applescript +122 -0
- package/dist/skills/powerpoint-architect/macos/scripts/autofit-placeholders.applescript +62 -0
- package/dist/skills/powerpoint-architect/macos/scripts/close-presentation.applescript +24 -0
- package/dist/skills/powerpoint-architect/macos/scripts/copy-slides.applescript +303 -0
- package/dist/skills/powerpoint-architect/macos/scripts/create-chart-with-data.applescript +305 -0
- package/dist/skills/powerpoint-architect/macos/scripts/create-with-theme.applescript +56 -0
- package/dist/skills/powerpoint-architect/macos/scripts/delete-slides.applescript +137 -0
- package/dist/skills/powerpoint-architect/macos/scripts/export-presentation.applescript +100 -0
- package/dist/skills/powerpoint-architect/macos/scripts/extract-slide-data.applescript +138 -0
- package/dist/skills/powerpoint-architect/macos/scripts/format-shape.applescript +192 -0
- package/dist/skills/powerpoint-architect/macos/scripts/format-slide-content.applescript +336 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-current-slide-number.applescript +38 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-file-path.applescript +94 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-layout-elements.applescript +141 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-layouts.applescript +58 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-opened-files.applescript +50 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-presentation-info.applescript +150 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-recent-files.applescript +68 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-slide-count.applescript +37 -0
- package/dist/skills/powerpoint-architect/macos/scripts/get-slide-info.applescript +105 -0
- package/dist/skills/powerpoint-architect/macos/scripts/health-check.applescript +690 -0
- package/dist/skills/powerpoint-architect/macos/scripts/insert-shape.applescript +188 -0
- package/dist/skills/powerpoint-architect/macos/scripts/insert-table.applescript +112 -0
- package/dist/skills/powerpoint-architect/macos/scripts/insert-text-box.applescript +225 -0
- package/dist/skills/powerpoint-architect/macos/scripts/manage-image.applescript +486 -0
- package/dist/skills/powerpoint-architect/macos/scripts/maximize-window.applescript +48 -0
- package/dist/skills/powerpoint-architect/macos/scripts/navigate-to-slide.applescript +84 -0
- package/dist/skills/powerpoint-architect/macos/scripts/open-presentation.applescript +38 -0
- package/dist/skills/powerpoint-architect/macos/scripts/reorder-slides.applescript +106 -0
- package/dist/skills/powerpoint-architect/macos/scripts/replace-text.applescript +193 -0
- package/dist/skills/powerpoint-architect/macos/scripts/save-presentation.applescript +54 -0
- package/dist/skills/powerpoint-architect/macos/scripts/set-animation.applescript +203 -0
- package/dist/skills/powerpoint-architect/macos/scripts/set-transition.applescript +130 -0
- package/dist/skills/powerpoint-architect/visual-styling-guide.md +206 -0
- package/dist/skills/powerpoint-architect/windows/api/advanced.md +317 -0
- package/dist/skills/powerpoint-architect/windows/api/basic.md +392 -0
- package/dist/skills/powerpoint-architect/windows/examples/10-slide-presentation.md +140 -0
- package/dist/skills/powerpoint-architect/windows/examples/custom-theme-workflow.md +219 -0
- package/dist/skills/powerpoint-architect/windows/examples/level-1-workflows.md +531 -0
- package/dist/skills/powerpoint-architect/windows/examples/level-2-scripting.md +239 -0
- package/dist/skills/powerpoint-architect/windows/scripts/create-with-theme.ps1 +81 -0
- package/dist/skills/project-task-list/SKILL.md +174 -0
- package/dist/skills/slack-operation/SKILL.md +97 -0
- package/dist/skills/slack-operation/api/advanced-api/GUIDE.md +277 -0
- package/dist/skills/slack-operation/api/search-and-read/EXAMPLE.md +75 -0
- package/dist/skills/slack-operation/api/search-and-read/GUIDE.md +108 -0
- package/dist/skills/slack-operation/api/send-message/EXAMPLE.md +112 -0
- package/dist/skills/slack-operation/api/send-message/GUIDE.md +63 -0
- package/dist/skills/slack-operation/api/share-files/EXAMPLE.md +94 -0
- package/dist/skills/slack-operation/api/share-files/GUIDE.md +63 -0
- package/dist/skills/slack-operation/ui/desktop-automation/GUIDE.md +55 -0
- package/dist/skills/system-diagnostics/SKILL.md +263 -0
- package/dist/skills/teams-operation/SKILL.md +79 -0
- package/dist/skills/teams-operation/api/advanced-api/GUIDE.md +234 -0
- package/dist/skills/teams-operation/api/meetings/EXAMPLE.md +63 -0
- package/dist/skills/teams-operation/api/meetings/GUIDE.md +52 -0
- package/dist/skills/teams-operation/api/search-and-read/EXAMPLE.md +72 -0
- package/dist/skills/teams-operation/api/search-and-read/GUIDE.md +54 -0
- package/dist/skills/teams-operation/api/send-message/EXAMPLE.md +92 -0
- package/dist/skills/teams-operation/api/send-message/GUIDE.md +60 -0
- package/dist/skills/teams-operation/ui/desktop-automation/GUIDE.md +66 -0
- package/dist/skills/transcribe-media/SKILL.md +142 -0
- package/dist/skills/uipath-integrations/SKILL.md +370 -0
- package/dist/skills/uipath-integrations/reference/connectors.md +331 -0
- package/dist/skills/uipath-integrations/reference/endpoints.md +220 -0
- package/dist/skills/uipath-integrations/reference/errors.md +211 -0
- package/dist/skills/uipath-integrations/reference/metadata.md +317 -0
- package/dist/skills/uipath-integrations/reference/operations.md +297 -0
- package/dist/skills/uipath-orchestrator/SKILL.md +312 -0
- package/dist/skills/uipath-orchestrator/recipes/assets.md +282 -0
- package/dist/skills/uipath-orchestrator/recipes/audit-logs.md +215 -0
- package/dist/skills/uipath-orchestrator/recipes/buckets.md +205 -0
- package/dist/skills/uipath-orchestrator/recipes/jobs.md +286 -0
- package/dist/skills/uipath-orchestrator/recipes/list-folders.md +207 -0
- package/dist/skills/uipath-orchestrator/recipes/queue-items.md +292 -0
- package/dist/skills/uipath-orchestrator/recipes/queues.md +232 -0
- package/dist/skills/uipath-orchestrator/recipes/releases.md +212 -0
- package/dist/skills/uipath-orchestrator/recipes/robots-sessions.md +274 -0
- package/dist/skills/uipath-orchestrator/recipes/schedules.md +280 -0
- package/dist/skills/uipath-orchestrator/reference/endpoints.md +85 -0
- package/dist/skills/uipath-orchestrator/reference/schemas.md +153 -0
- package/dist/skills/uipath-taskautomation/SKILL.md +310 -0
- package/dist/skills/uipath-taskautomation/assets/CodedWorkflow.template.cs +98 -0
- package/dist/skills/uipath-taskautomation/assets/ExampleWorkflow.cs +146 -0
- package/dist/skills/uipath-taskautomation/references/action-activity-map.json +32 -0
- package/dist/skills/uipath-taskautomation/references/action-activity-map.md +44 -0
- package/dist/skills/uipath-taskautomation/references/app-profiles.md +63 -0
- package/dist/skills/uipath-taskautomation/references/automation-spec.md +88 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/assets/before-after-hooks-template.md +115 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/assets/codedworkflow-template.md +186 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/assets/helper-utility-template.md +22 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/assets/json-template.md +91 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/assets/testcase-template.md +92 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/cli-reference.md +249 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/coded/codedworkflow-reference.md +275 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/coded/coding-guidelines.md +229 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/coded/inspect-package-guide.md +81 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/coded/integration-service-guide.md +507 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/coded/operations-guide.md +410 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/coded/third-party-packages-guide.md +67 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/data-manipulation-guide.md +110 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/environment-setup.md +194 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/error-handling-guide.md +195 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/powershell-interop-guide.md +57 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/project-structure-guide.md +114 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/project-structure.md +126 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/uia-elements-interaction-guide.md +109 -0
- package/dist/skills/uipath-taskautomation/references/coded-reference/validation-guide.md +147 -0
- package/dist/skills/uipath-taskautomation/references/coded-workflow-authoring.md +219 -0
- package/dist/skills/uipath-taskautomation/references/profiling-output.md +80 -0
- package/dist/skills/uipath-taskautomation/references/reliability-guide.md +83 -0
- package/dist/skills/uipath-taskautomation/references/task-automation-cheatsheet.md +272 -0
- package/dist/skills/uipath-taskautomation/references/template-preflight.md +17 -0
- package/dist/skills/uipath-workflow-documenter/SKILL.md +430 -0
- package/dist/skills/uipath-workflow-documenter/layouts/pdd-template.md +265 -0
- package/dist/skills/uipath-workflow-documenter/routines/from-orchestrator.md +11 -0
- package/dist/skills/uipath-workflow-documenter/routines/from-workflow.md +11 -0
- package/dist/skills/word-architect/SKILL.macos.md +147 -0
- package/dist/skills/word-architect/SKILL.md +502 -0
- package/dist/skills/word-architect/SKILL.windows.md +55 -0
- package/dist/skills/word-architect/api/advanced.md +522 -0
- package/dist/skills/word-architect/api/basic.md +378 -0
- package/dist/skills/word-architect/api/expert.md +302 -0
- package/dist/skills/word-architect/generation.md +308 -0
- package/dist/skills/word-architect/layouts/01-professional.md +168 -0
- package/dist/skills/word-architect/layouts/02-educational-kids.md +354 -0
- package/dist/skills/word-architect/layouts/03-academic.md +83 -0
- package/dist/skills/word-architect/layouts/04-creative.md +242 -0
- package/dist/skills/word-architect/layouts/05-operational.md +94 -0
- package/dist/skills/word-architect/macos/scripts/apply-heading-style.applescript +215 -0
- package/dist/skills/word-architect/macos/scripts/apply-style.applescript +272 -0
- package/dist/skills/word-architect/macos/scripts/autofit-tables.applescript +53 -0
- package/dist/skills/word-architect/macos/scripts/close-document.applescript +287 -0
- package/dist/skills/word-architect/macos/scripts/create-chart-with-data.applescript +379 -0
- package/dist/skills/word-architect/macos/scripts/create-chart.applescript +191 -0
- package/dist/skills/word-architect/macos/scripts/delete-selection.applescript +223 -0
- package/dist/skills/word-architect/macos/scripts/export-document.applescript +167 -0
- package/dist/skills/word-architect/macos/scripts/extract-table.applescript +168 -0
- package/dist/skills/word-architect/macos/scripts/find-by-style.applescript +173 -0
- package/dist/skills/word-architect/macos/scripts/find-text.applescript +199 -0
- package/dist/skills/word-architect/macos/scripts/format-table.applescript +234 -0
- package/dist/skills/word-architect/macos/scripts/format-text.applescript +431 -0
- package/dist/skills/word-architect/macos/scripts/get-document-properties.applescript +95 -0
- package/dist/skills/word-architect/macos/scripts/get-document-structure.applescript +371 -0
- package/dist/skills/word-architect/macos/scripts/get-header-footer-text.applescript +106 -0
- package/dist/skills/word-architect/macos/scripts/get-images.applescript +166 -0
- package/dist/skills/word-architect/macos/scripts/get-opened-files.applescript +103 -0
- package/dist/skills/word-architect/macos/scripts/get-paragraph-bounds.applescript +133 -0
- package/dist/skills/word-architect/macos/scripts/get-paragraph-format.applescript +134 -0
- package/dist/skills/word-architect/macos/scripts/get-recent-files.applescript +82 -0
- package/dist/skills/word-architect/macos/scripts/get-styled-text.applescript +256 -0
- package/dist/skills/word-architect/macos/scripts/get-tables.applescript +126 -0
- package/dist/skills/word-architect/macos/scripts/get-text-formatting.applescript +224 -0
- package/dist/skills/word-architect/macos/scripts/get-text.applescript +383 -0
- package/dist/skills/word-architect/macos/scripts/get-theme-colors.applescript +123 -0
- package/dist/skills/word-architect/macos/scripts/health-check.applescript +606 -0
- package/dist/skills/word-architect/macos/scripts/insert-cover-page.applescript +77 -0
- package/dist/skills/word-architect/macos/scripts/insert-header-footer.applescript +87 -0
- package/dist/skills/word-architect/macos/scripts/insert-horizontal-line.applescript +112 -0
- package/dist/skills/word-architect/macos/scripts/insert-html.applescript +440 -0
- package/dist/skills/word-architect/macos/scripts/insert-hyperlink.applescript +191 -0
- package/dist/skills/word-architect/macos/scripts/insert-image.applescript +320 -0
- package/dist/skills/word-architect/macos/scripts/insert-list.applescript +317 -0
- package/dist/skills/word-architect/macos/scripts/insert-pagebreak.applescript +181 -0
- package/dist/skills/word-architect/macos/scripts/insert-smartart.applescript +104 -0
- package/dist/skills/word-architect/macos/scripts/insert-table.applescript +238 -0
- package/dist/skills/word-architect/macos/scripts/insert-text.applescript +677 -0
- package/dist/skills/word-architect/macos/scripts/insert-textbox.applescript +261 -0
- package/dist/skills/word-architect/macos/scripts/maximize-window.applescript +67 -0
- package/dist/skills/word-architect/macos/scripts/normalize-formatting.applescript +56 -0
- package/dist/skills/word-architect/macos/scripts/open-document.applescript +222 -0
- package/dist/skills/word-architect/macos/scripts/replace-text.applescript +390 -0
- package/dist/skills/word-architect/macos/scripts/save-document.applescript +230 -0
- package/dist/skills/word-architect/macos/scripts/select-range.applescript +142 -0
- package/dist/skills/word-architect/macos/scripts/set-document-properties.applescript +195 -0
- package/dist/skills/word-architect/macos/scripts/set-page-layout.applescript +273 -0
- package/dist/skills/word-architect/macos/scripts/set-theme-colors.applescript +264 -0
- package/dist/skills/word-architect/macos/scripts/undo-redo.applescript +61 -0
- package/dist/skills/word-architect/macos/scripts/update-toc.applescript +112 -0
- package/dist/skills/word-architect/reference/formatting.md +119 -0
- package/dist/skills/word-architect/reference/html-layouts/01-executive-summary-box.md +36 -0
- package/dist/skills/word-architect/reference/html-layouts/02-kpi-summary-table.md +68 -0
- package/dist/skills/word-architect/reference/html-layouts/03-comparison-table.md +63 -0
- package/dist/skills/word-architect/reference/html-layouts/04-pros-cons-table.md +86 -0
- package/dist/skills/word-architect/reference/html-layouts/05-timeline-table.md +114 -0
- package/dist/skills/word-architect/reference/html-layouts/06-raci-matrix.md +95 -0
- package/dist/skills/word-architect/reference/html-layouts/07-data-table-alternating.md +84 -0
- package/dist/skills/word-architect/reference/html-layouts/08-callout-box.md +102 -0
- package/dist/skills/word-architect/reference/html-layouts/09-vertical-milestone.md +100 -0
- package/dist/skills/word-architect/reference/quality-assurance.md +102 -0
- package/dist/skills/word-architect/reference/tables.md +62 -0
- package/dist/skills/word-architect/reference/tracked-changes.md +34 -0
- package/dist/skills/word-architect/reference/uia-fallback.md +231 -0
- package/dist/skills/word-architect/reference/visual-elements.md +82 -0
- package/dist/skills/word-architect/windows/scripts/apply-heading-style.ps1 +190 -0
- package/dist/skills/word-architect/windows/scripts/autofit-tables.ps1 +64 -0
- package/dist/skills/word-architect/windows/scripts/create-chart-with-data.ps1 +133 -0
- package/dist/skills/word-architect/windows/scripts/create-chart.ps1 +73 -0
- package/dist/skills/word-architect/windows/scripts/export-document.ps1 +86 -0
- package/dist/skills/word-architect/windows/scripts/get-current-file.ps1 +27 -0
- package/dist/skills/word-architect/windows/scripts/insert-cover-page.ps1 +79 -0
- package/dist/skills/word-architect/windows/scripts/insert-horizontal-line.ps1 +74 -0
- package/dist/skills/word-architect/windows/scripts/insert-image.ps1 +98 -0
- package/dist/skills/word-architect/windows/scripts/insert-smartart.ps1 +118 -0
- package/dist/skills/word-architect/windows/scripts/insert-text-box.ps1 +90 -0
- package/dist/skills/word-architect/windows/scripts/normalize-formatting.ps1 +63 -0
- package/package.json +5 -4
|
@@ -0,0 +1,274 @@
|
|
|
1
|
+
# Phase 2 — BPMN TO-BE Design
|
|
2
|
+
|
|
3
|
+
User-facing wording: business terms only (current process, future process, process map, completeness check). Internal labels in this guide are for you, never spoken to the user unless the user already uses "BPMN" or asks for product/category language.
|
|
4
|
+
|
|
5
|
+
Use this guide when Decision 2 — the Case-vs-BPMN routing question that opens TO-BE for processes (SKILL.md Opening Discovery Router; skipped only when the user already named the target) — lands on BPMN. Existing BPMN work enters here after AS-IS is confirmed. New BPMN work starts here directly; do not invent AS-IS pages for a process that does not exist yet.
|
|
6
|
+
|
|
7
|
+
## What This Phase Produces
|
|
8
|
+
|
|
9
|
+
```
|
|
10
|
+
to-be/overview.md # framing + link/reference to the BPMN process model
|
|
11
|
+
to-be/process.bpmn # BPMN 2.0 semantic XML without BPMNDI layout; process model of record
|
|
12
|
+
to-be/bpmn-details.md # process objective, modeling scope, start/end events, terminal outcomes
|
|
13
|
+
to-be/transformation-decisions.md # AS-IS issue | proposed TO-BE change | user decision
|
|
14
|
+
to-be/participants-and-lanes.md # participants, lanes, owners, handoff responsibility
|
|
15
|
+
to-be/events-and-triggers.md # start events, end events, timers, messages, escalations
|
|
16
|
+
to-be/activities.md # activities/subprocesses with owner, system, inputs, outputs
|
|
17
|
+
to-be/gateways-and-routes.md # decisions, split/merge behavior, rework, terminal routes
|
|
18
|
+
to-be/business-rules.md # new or changed future-state rules and gateway conditions
|
|
19
|
+
to-be/message-and-timer-flows.md # messages, waits, timers, callbacks, deadlines
|
|
20
|
+
to-be/data-objects.md # records, artifacts, evidence, data stores
|
|
21
|
+
to-be/exception-handling.md # exception paths and recovery routes
|
|
22
|
+
to-be/benefits.md # qualitative business outcomes
|
|
23
|
+
to-be/kpis.md # numeric: one row per KPI — AS-IS baseline, target, acceptance signal, owner
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
**What marks this phase successful.** `to-be/process.bpmn` exists on disk when the phase closes, parses as real XML, carries a `bpmn:definitions` root and a process, and resolves every model reference it declares — one unresolvable `sourceRef`, `targetRef` or `default` leaves the model unreadable to anything downstream. Every outgoing route of a split gateway is labelled, conditioned, or declared as that gateway's default route; a join with a single outgoing flow is not a split and needs none. The model carries an element for every participant, activity, gateway and wait the pages behind it define.
|
|
27
|
+
|
|
28
|
+
## Entry Guard
|
|
29
|
+
|
|
30
|
+
If this is Existing + BPMN and neither `as-is/process.bpmn`, canonical `as-is/diagram.md`, nor legacy `as-is/overview.md` has a user-confirmed current process map, refuse entry in business terms: *"Let's finish the current process first so the future design has a stable baseline."*
|
|
31
|
+
|
|
32
|
+
If this is New + BPMN, begin here and record in `to-be/bpmn-details.md` that this is a net-new process model with no current-state process. The PDD Current State section uses that fact to say AS-IS is not applicable. Do not create fake AS-IS detail.
|
|
33
|
+
|
|
34
|
+
## BPMN-vs-Case Choice Checkpoint (mid-phase escape hatch)
|
|
35
|
+
|
|
36
|
+
The routing question already decided BPMN at the phase open; this checkpoint exists for a **genuine later contradiction** — evidence emerging during the workshop that Case fits better. Use it only when:
|
|
37
|
+
- the user asks whether this should be Case instead of BPMN;
|
|
38
|
+
- the workshop reveals a tracked request/object with stages, owners, SLAs, evidence, and terminal outcomes that the routing evidence did not show;
|
|
39
|
+
- the user appears more comfortable with Case terminology than BPMN terminology.
|
|
40
|
+
|
|
41
|
+
If BPMN still looks like the best fit but Case is plausible, use one AskUser call with finite options:
|
|
42
|
+
|
|
43
|
+
```
|
|
44
|
+
Question: "This looks most like a BPMN process model because it spans participants, handoffs, events, and decisions. It could also be designed as a Case if you want to manage a long-running request or object through stages, owners, SLAs, and outcomes. Which process document should I build?"
|
|
45
|
+
Options:
|
|
46
|
+
- BPMN process model (Recommended) — Use when the priority is a cross-functional process map with events, gateways, waits, and handoffs.
|
|
47
|
+
- Case design — Use when the priority is lifecycle management for a request/object with stages, owners, SLAs, evidence, and terminal outcomes.
|
|
48
|
+
```
|
|
49
|
+
|
|
50
|
+
If the user picks Case, stop this guide and read `case-to-be-design.md`. If the user picks BPMN, continue here. If the user explicitly asked for Case before this checkpoint, honor Case without trying to steer them back.
|
|
51
|
+
|
|
52
|
+
## Move 1 — Pre-read AS-IS BPMN Baseline
|
|
53
|
+
|
|
54
|
+
For Existing + BPMN, read `as-is/process.bpmn` when it exists, canonical `as-is/diagram.md` when present, `as-is/overview.md`, `as-is/steps/`, `as-is/scheduling-and-triggers.md`, `as-is/data-inputs-outputs.md`, `as-is/exception-handling.md`, `as-is/pain-points.md`, `entities/applications/`, `entities/people/`, and any `to-be/seeds.md` created during AS-IS. Treat a supplied `as-is/process.bpmn` as the current-state process model of record; do not alter it while designing the future state.
|
|
55
|
+
|
|
56
|
+
Normalize AS-IS into BPMN dimensions:
|
|
57
|
+
- current participants and lanes
|
|
58
|
+
- start event and terminal outcomes
|
|
59
|
+
- activities and subprocesses
|
|
60
|
+
- handoffs between participants
|
|
61
|
+
- gateways, decisions, and merge points
|
|
62
|
+
- messages, waits, timers, callbacks, and escalations
|
|
63
|
+
- systems and data objects
|
|
64
|
+
- exceptions, rework, and recovery routes
|
|
65
|
+
- volume / frequency / backlog
|
|
66
|
+
- cycle time / SLA
|
|
67
|
+
- AS-IS gaps and pain points
|
|
68
|
+
|
|
69
|
+
Convert the baseline into a target-change proposal table. Write `to-be/transformation-decisions.md` with columns: `AS-IS area | AS-IS issue | Proposed target change | User decision | Notes`.
|
|
70
|
+
|
|
71
|
+
Present the proposed target changes inside the Future Process Review as "Proposed changes from today's process" — one confirmation covers the changes and the model together; do not run a separate target-change confirmation round. If a proposed change is genuinely uncertain and shape-defining, it joins the batched blocking questions.
|
|
72
|
+
|
|
73
|
+
For New + BPMN, skip AS-IS normalization and start with the progressive BPMN workshop.
|
|
74
|
+
|
|
75
|
+
## Progressive Process Knowledge During TO-BE
|
|
76
|
+
|
|
77
|
+
Latched run first (SKILL.md, The latch): `{WikiPath}/research-pass.md` records `Process Knowledge state:` `closed` or `opted-out` → make none of the calls below, log `Phase: TO-BE — skipped` once in `process-knowledge.md`, and this phase's checkpoint is complete. Never send a decision to unlock them.
|
|
78
|
+
|
|
79
|
+
Use Process Knowledge for process-model design suggestions: likely participants, activities, gateway outcomes, message/timer waits, exception routes, controls, and SLA patterns. Confirmed user facts and wiki content remain the source of truth.
|
|
80
|
+
|
|
81
|
+
Call it at these TO-BE checkpoints:
|
|
82
|
+
|
|
83
|
+
1. **Before Move 2 BPMN workshop.** Include matched process display names, current AS-IS summary when present, the process goal, systems, participants, and known constraints. Ask for likely participants/lanes, activities, decisions, waits, exception routes, controls, and SLAs.
|
|
84
|
+
2. **After drafting target changes for Existing + BPMN, or after the first process sketch for New + BPMN.** Include the proposed participants, activities, and gateways. Ask for missing activities, handoff gaps, unresolved gateway outcomes, missing waits, and exception routes.
|
|
85
|
+
3. **Before drafting the BPMN model.** Ask for a target-state completeness check: missing activities, terminal outcomes, rework loops, exception paths, timers, handoffs, audit evidence, and fallback paths.
|
|
86
|
+
4. **Before PDD readiness.** Ask for PDD-facing terminology, KPIs, controls, glossary terms, exception language, and any residual completeness gaps.
|
|
87
|
+
|
|
88
|
+
For follow-up calls, keep the same API shape and put the context into the `description`:
|
|
89
|
+
|
|
90
|
+
```text
|
|
91
|
+
Continue using these matched process references: <display names from process-knowledge.md>.
|
|
92
|
+
Confirmed current process: <brief AS-IS summary, or net-new with no AS-IS>.
|
|
93
|
+
Proposed future process model so far: <participants, activities, gateways, waits, exceptions>.
|
|
94
|
+
Need now: process-model best practices, missing handoffs, gateway outcomes, exception patterns, SLA guidance, and PDD terminology.
|
|
95
|
+
```
|
|
96
|
+
|
|
97
|
+
When using returned best practices, turn them into confirm-or-change options. Do not write a reference participant, activity, wait, or exception route into `to-be/` unless it fits the user's scope and has been confirmed or recorded as an explicit assumption/open item.
|
|
98
|
+
|
|
99
|
+
Phase gate: follow the Gate's fit judgment (SKILL.md) for whether to call again here, never while the latch holds. When you do, append to `process-knowledge.md` a new entry with `Phase: TO-BE` and the result status before presenting proposed participants or target changes, drafting the BPMN model, or writing `to-be/` files. If the call errors, retry once; if the retry also errors, record the error in `process-knowledge.md` and ask the user whether to continue from confirmed AS-IS/source facts.
|
|
100
|
+
|
|
101
|
+
## Move 2 — Progressive BPMN Workshop
|
|
102
|
+
|
|
103
|
+
Listen first. Ask the user to describe the future process in business terms: what starts it, which participants are involved, what work happens, where decisions happen, what waits or messages occur, and how the process ends.
|
|
104
|
+
|
|
105
|
+
Sketch privately. Infer the process shape from what the user said and from AS-IS if present, then ask anchored confirm-or-change questions. Do not ask a cold questionnaire; show what you think you have, then ask the smallest next question.
|
|
106
|
+
|
|
107
|
+
Run this progressive BPMN workshop in order:
|
|
108
|
+
|
|
109
|
+
| # | Dimension | When to ask | What to capture |
|
|
110
|
+
|---|---|---|---|
|
|
111
|
+
| 1 | process objective and scope | Opening TO-BE context | Business goal, included process boundaries, excluded subprocesses |
|
|
112
|
+
| 2 | participants and lanes | shape-defining questions before the map | Departments, roles, systems, external parties, handoff ownership |
|
|
113
|
+
| 3 | start and end events | shape-defining questions before the map | Trigger, alternate starts, terminal outcomes |
|
|
114
|
+
| 4 | activities and subprocesses | shape-defining questions before the map | Work activities, natural subprocess boundaries, owner/system |
|
|
115
|
+
| 5 | gateways and routes | shape-defining questions before the map | Decision outcomes, splits, merges, parallel work, rework loops |
|
|
116
|
+
| 6 | messages and timers | shape-defining questions before the map | Message sends/receives, callbacks, waits, deadlines, escalation timers |
|
|
117
|
+
| 7 | data objects and systems | detail questions after the map | Records, artifacts, evidence, source of truth, read/write systems |
|
|
118
|
+
| 8 | exceptions and escalations | shape-defining questions before the map | Error events, interrupting paths, recovery routes, terminal failure |
|
|
119
|
+
| 9 | SLA and timing | detail questions after the map | Overall process SLA, milestone deadlines, timer events |
|
|
120
|
+
| 10 | volume / backlog | detail questions after the map | Volume, peaks, backlog, aging risk, capacity pressure |
|
|
121
|
+
| 11 | compliance and policy | detail questions after the map | Policy constraints, regulated decisions, audit evidence |
|
|
122
|
+
|
|
123
|
+
Rows 2, 3, 4, 5, 6, and 8 define the BPMN shape. Do not skip them unless AS-IS or user-provided documents captured the answer verbatim and you have reflected it back for confirmation.
|
|
124
|
+
|
|
125
|
+
Before generating the PDD, run a completeness check: unresolved participants/lanes, missing start/end events, missing gateway outcomes, unclear message/timer waits, missing exception routes, and unknown terminal outcomes must either be answered or recorded as explicit open questions.
|
|
126
|
+
|
|
127
|
+
## Move 3 — Synchronize, Then Draft the BPMN Model
|
|
128
|
+
|
|
129
|
+
**TaskList synchronization gate.** Before writing `to-be/process.bpmn`, make the next mutation one `project-task-list` update of every affected ANALYSIS row in `TaskListPath` (participants/lanes, activities, gateways, waits, systems, exceptions, SLAs captured so far), with the intended answers, provenance, and statuses. Do not write the model while any affected ANALYSIS row is stale.
|
|
130
|
+
|
|
131
|
+
Draft `to-be/process.bpmn` before drafting the detailed pages. This is the process model of record. It must be valid BPMN 2.0 semantic XML. Do not include BPMNDI: Delegate creates deterministic BPMNDI layout in memory before live, PDD, and Word rendering.
|
|
132
|
+
|
|
133
|
+
### Documentation BPMN profile
|
|
134
|
+
|
|
135
|
+
Author a portable, non-executable process model that can be rendered consistently by Delegate and UiPath Maestro / PO.Frontend. Set every generated `bpmn:process` to `isExecutable="false"`. Do not invent `uipath:*` execution extensions, activity bindings, variables, schemas, retry settings, package identifiers, or service types. Those fields configure an executable Maestro process and cannot be inferred safely from a business-analysis workshop. Express the intended UiPath implementation through the most specific standard BPMN task type and its business label, then record the product choice, system, inputs, and outputs in `to-be/activities.md`.
|
|
136
|
+
|
|
137
|
+
The LLM owns process semantics; Delegate owns geometry. Do not emit `bpmndi:*`, `dc:Bounds`, `di:waypoint`, or `bpmndi:BPMNLabel`. Delegate deterministically generates BPMNDI in memory.
|
|
138
|
+
|
|
139
|
+
The semantic model must be complete:
|
|
140
|
+
- every participant that owns a process has a valid `processRef`;
|
|
141
|
+
- every lane lists its contained flow nodes with `flowNodeRef`, and each flow node belongs to no more than one lane in that lane set;
|
|
142
|
+
- every sequence flow has valid `sourceRef` and `targetRef`; incoming/outgoing declarations are optional because Delegate reconstructs them when it lays out the model;
|
|
143
|
+
- boundary events set `attachedToRef`; omit `cancelActivity` for the default interrupting form and set `cancelActivity="false"` only for a non-interrupting boundary event;
|
|
144
|
+
- every timer event definition contains exactly one concrete `bpmn:timeDate`, `bpmn:timeDuration`, or `bpmn:timeCycle` expression. Never emit an empty `bpmn:timerEventDefinition`;
|
|
145
|
+
- a decision-table condition (AS-IS `Decision points`) is a `bpmn:exclusiveGateway` with one named outgoing flow per outcome; work that runs independently is a `bpmn:parallelGateway` split with a matching join, never chained tasks; distinct outcomes are distinct tasks or end events;
|
|
146
|
+
- conditional routes carry a `bpmn:conditionExpression`, and one outgoing sequence flow may use the gateway or activity `default` attribute when the business rule defines a fallback route.
|
|
147
|
+
|
|
148
|
+
Use the same BPMN element families supported by UiPath Maestro / PO.Frontend's rich canvas.
|
|
149
|
+
These are the tag names verbatim: BPMN element names are case-sensitive, and a PascalCase
|
|
150
|
+
spelling is valid XML that no BPMN tool recognizes as the same element — it parses and then
|
|
151
|
+
renders nothing:
|
|
152
|
+
- participants/pools and lanes: `bpmn:participant`, `bpmn:lane`
|
|
153
|
+
- events: `bpmn:startEvent`, `bpmn:intermediateCatchEvent`, `bpmn:intermediateThrowEvent`, `bpmn:boundaryEvent`, `bpmn:endEvent`
|
|
154
|
+
- activities: `bpmn:task`, `bpmn:userTask`, `bpmn:serviceTask`, `bpmn:sendTask`, `bpmn:receiveTask`, `bpmn:manualTask`, `bpmn:businessRuleTask`, `bpmn:scriptTask`, `bpmn:callActivity`, `bpmn:subProcess`
|
|
155
|
+
- gateways: `bpmn:exclusiveGateway`, `bpmn:parallelGateway`, `bpmn:inclusiveGateway`, `bpmn:eventBasedGateway`, `bpmn:complexGateway`
|
|
156
|
+
- flows: `bpmn:sequenceFlow`, `bpmn:messageFlow`
|
|
157
|
+
|
|
158
|
+
Author semantically as BPMN, not as a flowchart. Use events, activities, gateways, pools, lanes, sequence flows, and message flows to express the process. The renderer supplies BPMN notation, label wrapping, routing, and geometry.
|
|
159
|
+
|
|
160
|
+
The generated BA profile does not include `bpmn:textAnnotation`, `bpmn:group`, `bpmn:association`, `bpmn:dataInputAssociation`, or `bpmn:dataOutputAssociation`; record that supporting detail in the related Markdown source instead. Delegate preserves valid source geometry for an imported model only when the upstream layout engine cannot represent one of those existing elements.
|
|
161
|
+
|
|
162
|
+
### Mandatory saved-artifact validation
|
|
163
|
+
|
|
164
|
+
After writing `to-be/process.bpmn`, validate the saved file before writing `to-be/overview.md`, asking for map confirmation, or starting the PDD. Do not treat a visually plausible XML string as valid.
|
|
165
|
+
|
|
166
|
+
1. Parse the saved file with a real XML parser. Prefer `xmllint --noout <absolute-process.bpmn-path>` when available. Otherwise use a standard-library parser such as Python `xml.etree.ElementTree.parse`. A text search, regex check, or re-reading the XML is not a parse validation.
|
|
167
|
+
2. If parsing fails, fix the source and run the parser again. XML-reserved characters inside labels and attributes must be escaped, including `<` as `<`, `>` as `>` when needed, `&` as `&`, and quotes with the matching XML entity when they occur inside the same quote-delimited attribute.
|
|
168
|
+
3. Validate model references: every `sourceRef`, `targetRef`, `processRef`, `attachedToRef`, and `flowNodeRef` resolves to an existing compatible BPMN element; every sequence flow appears in the referenced nodes' incoming/outgoing declarations when those declarations are present.
|
|
169
|
+
4. Validate reachability, not just references — a model can parse cleanly and still be unrunnable. Every end event has at least one incoming sequence flow; every task and gateway has both an incoming and an outgoing flow, except the start event (no incoming) and end events (no outgoing); every branch a parallel gateway opens is joined by a matching parallel join, and every path into a join is reachable from the start event, so no join can wait forever on a branch that never runs; every exception and escalation route named in `to-be/exception-handling.md` terminates in a reachable end event. Walk the flows from the start event and list any node you never reach — an orphan task or an end state with no incoming flow means that path is dead in the model even though the prose describes it.
|
|
170
|
+
5. Do not validate or generate BPMNDI coverage. Delegate deterministically adds geometry at render time.
|
|
171
|
+
6. Re-run the XML parser after all semantic-reference fixes. Do not proceed while any validation error remains, and report the exact failing element if the artifact cannot be repaired.
|
|
172
|
+
|
|
173
|
+
Then write `to-be/overview.md` with a 2-3 sentence framing summary, a link/action to open the TO-BE diagram, and a brief note that `to-be/process.bpmn` is the source of truth. Do not put a Mermaid block in `to-be/overview.md` for BPMN routes.
|
|
174
|
+
|
|
175
|
+
Minimal BPMN file shape:
|
|
176
|
+
|
|
177
|
+
````
|
|
178
|
+
<?xml version="1.0" encoding="UTF-8"?>
|
|
179
|
+
<bpmn:definitions
|
|
180
|
+
xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL"
|
|
181
|
+
id="Definitions_<slug>"
|
|
182
|
+
targetNamespace="https://uipath.com/business-analysis/<slug>">
|
|
183
|
+
<bpmn:collaboration id="Collaboration_<slug>">
|
|
184
|
+
<bpmn:participant id="Participant_Main" name="<process name>" processRef="Process_Main" />
|
|
185
|
+
</bpmn:collaboration>
|
|
186
|
+
<bpmn:process id="Process_Main" isExecutable="false">
|
|
187
|
+
<bpmn:startEvent id="Start_RequestReceived" name="Request received" />
|
|
188
|
+
<bpmn:userTask id="Task_ValidateRequest" name="Validate request" />
|
|
189
|
+
<bpmn:exclusiveGateway id="Gateway_CompleteEnough" name="Complete enough?" />
|
|
190
|
+
<bpmn:endEvent id="End_Complete" name="Complete" />
|
|
191
|
+
<bpmn:sequenceFlow id="Flow_Start_To_Validate" sourceRef="Start_RequestReceived" targetRef="Task_ValidateRequest" />
|
|
192
|
+
<bpmn:sequenceFlow id="Flow_Validate_To_Gateway" sourceRef="Task_ValidateRequest" targetRef="Gateway_CompleteEnough" />
|
|
193
|
+
<bpmn:sequenceFlow id="Flow_Gateway_To_End" sourceRef="Gateway_CompleteEnough" targetRef="End_Complete" />
|
|
194
|
+
</bpmn:process>
|
|
195
|
+
</bpmn:definitions>
|
|
196
|
+
````
|
|
197
|
+
|
|
198
|
+
**Close this phase on its output.** Before presenting the review, run the readiness check as the
|
|
199
|
+
last silent step — it lists what is still unwritten, and a review presented with the
|
|
200
|
+
pages missing has closed nothing:
|
|
201
|
+
|
|
202
|
+
```
|
|
203
|
+
bash "{BusinessAnalysisSkillDir}/scripts/check-phase-ready.sh" --wiki "{WikiPath}" --phase to-be --route bpmn
|
|
204
|
+
```
|
|
205
|
+
|
|
206
|
+
On Windows:
|
|
207
|
+
|
|
208
|
+
```
|
|
209
|
+
& "{BusinessAnalysisSkillDir}\scripts\check-phase-ready.ps1" -Wiki "{WikiPath}" -Phase to-be -Route bpmn
|
|
210
|
+
```
|
|
211
|
+
|
|
212
|
+
`PHASEREADY:ok` is the only result that closes the phase. On `PHASEREADY:not-ready`,
|
|
213
|
+
write the pages and columns it names from the facts you have already confirmed, then
|
|
214
|
+
run it again. It never writes anything, so re-running it is free, and it fails open
|
|
215
|
+
with `PHASEREADY:skipped` if it cannot resolve the wiki — which is not a pass.
|
|
216
|
+
|
|
217
|
+
### Write the model's own pages before the review
|
|
218
|
+
|
|
219
|
+
`to-be/process.bpmn` is the model of record; these five pages are what its elements mean. Write them here,
|
|
220
|
+
one page per `WriteFile`, while the model is in front of you — a participant, event, activity, gateway or
|
|
221
|
+
wait named on a page and missing from the model, or in the model and on no page, is the two disagreeing,
|
|
222
|
+
and the disagreement is cheapest to see now. Deferring them past the review also loses them outright
|
|
223
|
+
whenever the stakeholder is satisfied at the checkpoint, which ends the phase:
|
|
224
|
+
|
|
225
|
+
- `to-be/participants-and-lanes.md` — participants, lanes, responsibilities, handoff ownership.
|
|
226
|
+
- `to-be/events-and-triggers.md` — start events, end events, message events, timer events, escalation events.
|
|
227
|
+
- `to-be/activities.md` — activities/subprocesses; include owner, system, input, output, business rule, required completion.
|
|
228
|
+
- `to-be/gateways-and-routes.md` — gateway decisions, outcomes, splits/merges, rework loops, terminal routes.
|
|
229
|
+
- `to-be/message-and-timer-flows.md` — messages, waits, timers, callbacks, deadlines, escalation timers.
|
|
230
|
+
|
|
231
|
+
The remaining Move 4 pages describe the process around the model — rules, data, exceptions, benefits, KPIs —
|
|
232
|
+
and stay there.
|
|
233
|
+
|
|
234
|
+
Closing sequence — do all, in order, silently until step 3:
|
|
235
|
+
|
|
236
|
+
1. Run the readiness check above and clear it to `PHASEREADY:ok`, writing any page it names from facts already confirmed. A review sent before this has closed nothing, and the phase ends at step 2 whether or not the pages exist.
|
|
237
|
+
2. Record this phase's Process Knowledge checkpoint in `process-knowledge.md` — its phase, focus and result status — for every retrieval the phase made, including the ones that matched nothing. A call whose result was never written down is not a checkpoint, and the next session reads the file, not this conversation: an unrecorded retrieval is one the project has to make again.
|
|
238
|
+
3. **MANDATORY STOP — Future Process Review (the phase checkpoint).** Send it only after saved-artifact validation passes and after this phase's one self-review, which runs before the review and never after it (SKILL.md "One Review Per Phase"): one pass, one fix round, and whatever it still leaves goes into **Assumptions and open gaps** — never a second pass. Render the complete review body as normal assistant Markdown immediately before one AskUser call in the same turn. Use these fixed headings: **Future process**, **Participants and handoffs**, **Events, gateways, and waits**, **Exceptions and terminal outcomes**, **Proposed changes from today's process** (existing work only), and **Assumptions and open gaps**. The validated model (BPMN) is already visible beside this quick-glance review. Never compress the review into the AskUser `intro` or `question`; a short "model ready" recap is not the Future Process Review. AskUser contains only the final decision: *"Confirm / Change / Attach or record more evidence?"* Draft the remaining Move 4 pages only after the model is confirmed. Once the user confirms the model, stamp `verified` on the confirmed `to-be/` pages per SKILL.md Page Trust Stamps, and call `AskUserFeedback` with `checkpoint: 'ba.toBeCreated'` (one non-blocking call; do not announce it or wait for a rating; skip silently if the tool is unavailable).
|
|
239
|
+
|
|
240
|
+
## Move 4 — Draft BPMN Detail
|
|
241
|
+
|
|
242
|
+
After map confirmation, draft the rest of the `to-be/` folder (participants, events, activities, gateways and message/timer flows are already written, in Move 3):
|
|
243
|
+
|
|
244
|
+
- `to-be/bpmn-details.md` — process objective, modeling scope, trigger/start events, terminal outcomes.
|
|
245
|
+
- `to-be/process.bpmn` — BPMN 2.0 semantic XML source; Delegate generates layout.
|
|
246
|
+
- `to-be/transformation-decisions.md` — Existing + BPMN only; AS-IS issue, proposed target change, user decision, notes.
|
|
247
|
+
- `to-be/business-rules.md` — when a gateway condition or activity encodes a business rule, regulation, or customer requirement, record it here too: rule, enforcement point/gateway id, evidence, confirmed/open.
|
|
248
|
+
- `to-be/data-objects.md` — records, artifacts, evidence, data stores, retention.
|
|
249
|
+
- `to-be/exception-handling.md` — exception paths, owner, recovery path, terminal failure path.
|
|
250
|
+
- `to-be/benefits.md` — qualitative business outcomes only; no ROI math.
|
|
251
|
+
- `to-be/kpis.md` — the numeric artifact, one row per KPI: `KPI | AS-IS baseline (value + measurement method) | Target | Acceptance signal | Owner`. Carry each baseline figure verbatim from `as-is/metrics.md` with the measurement method beside it, and each target verbatim from the confirmed target discussion — never recompute, round, or derive either one. On net-new work there is no baseline: write `no current baseline (net-new)` in that cell and keep the target, the acceptance signal and the owner. Where a target was never discussed, keep the row with its baseline filled and write the target as a concrete open question rather than dropping the KPI. This file is where every number the document quotes as a target comes from: `benefits.md` stays qualitative, and a qualitative page cannot source PDD §1.2's baseline-and-target pair or §10's target table.
|
|
252
|
+
|
|
253
|
+
Append any new open items or carried assumptions from this phase to `queries/open-questions.md`. After each completed factual write round, make the next mutation one `project-task-list` update of every affected ANALYSIS row, with the intended answers, provenance, and statuses. Update `{WikiPath}/index.md` only after the detail pages and their task list synchronization boundaries are complete. Drafting these pages is free; changing a fact on a page the model confirmation stamped `verified` is named in chat, in the same reply that makes it (SKILL.md "Editing a confirmed page").
|
|
254
|
+
|
|
255
|
+
## Detail Quality Bar
|
|
256
|
+
|
|
257
|
+
The BPMN TO-BE must be specific enough for PDD Section 4 to describe and embed:
|
|
258
|
+
|
|
259
|
+
- the business process being modeled;
|
|
260
|
+
- the participants/lanes and handoff ownership;
|
|
261
|
+
- start events, end events, timer/message events, and terminal outcomes;
|
|
262
|
+
- activities and subprocesses;
|
|
263
|
+
- gateways, decision outcomes, splits, merges, and rework loops;
|
|
264
|
+
- systems, data objects, artifacts, and evidence;
|
|
265
|
+
- exception paths and escalation timers;
|
|
266
|
+
- SLA and timing constraints;
|
|
267
|
+
- volume / backlog constraints;
|
|
268
|
+
- the confirmed BPMN diagram from `to-be/process.bpmn`.
|
|
269
|
+
|
|
270
|
+
If any of these are unknown, ask before generating the PDD or mark the item as a concrete open question. Do not fill gaps with generic BPMN language.
|
|
271
|
+
|
|
272
|
+
## Closing Phase 2
|
|
273
|
+
|
|
274
|
+
The model confirmation closes the phase. State in one line that the process document can be generated whenever they're ready — the first ```sf chip carries `Generate the process document`. Do not ask an additional "generate now?" question; enter Phase 3 only on the user's explicit request.
|
|
@@ -0,0 +1,223 @@
|
|
|
1
|
+
# Phase 2 — Case TO-BE Design
|
|
2
|
+
|
|
3
|
+
User-facing wording: business terms only (current process, future process, process map, completeness check). Internal labels in this guide are for you, never spoken to the user.
|
|
4
|
+
|
|
5
|
+
Use this guide when Decision 2 — the Case-vs-BPMN routing question that opens TO-BE for processes (SKILL.md Opening Discovery Router; skipped only when the user already named the target) — lands on Case management. Existing Case work enters here after AS-IS is confirmed. New Case work starts here directly; do not invent AS-IS pages for a process that does not exist yet.
|
|
6
|
+
|
|
7
|
+
Terminology guard: Use "case work", "stage work", or "case activity" in user-facing wording. Reserve "case task" for product-internal detail, and use it only when the PDD needs to be precise about UiPath Case implementation concepts. In the BA skill, plain "task" means an RPA automation task.
|
|
8
|
+
|
|
9
|
+
## What This Phase Produces
|
|
10
|
+
|
|
11
|
+
```
|
|
12
|
+
to-be/overview.md # future-state framing prose
|
|
13
|
+
to-be/diagram.md # PDD-ready fenced Mermaid case map
|
|
14
|
+
to-be/case-details.md # case objective, lifecycle, typed trigger (manual / scheduled / external event + source), terminal outcomes
|
|
15
|
+
to-be/transformation-decisions.md # AS-IS issue | proposed TO-BE change | user decision
|
|
16
|
+
to-be/stages/ # one MD per stage (map-included or excluded), <stage-id>.md = the map's subgraph id: type, status, entry/exit, case work and tasks, owners, systems, SLA, decisions, exceptions, evidence — the sole source per stage, no separate ledger
|
|
17
|
+
to-be/decisions-and-routes.md # decisions, outcomes, rework, terminal routes
|
|
18
|
+
to-be/data-and-evidence.md # data, artifacts, evidence, retention
|
|
19
|
+
to-be/business-rules.md # new or changed future-state rules and case controls
|
|
20
|
+
to-be/exception-handling.md # exception stages and recovery paths
|
|
21
|
+
to-be/slas.md # SLA and timing by stage/case activity: target, at-risk warning point, response (notify whom vs change course into a stage)
|
|
22
|
+
to-be/personas.md # personas and owners, plus what each persona sees and does when they open the case (app view)
|
|
23
|
+
to-be/benefits.md # qualitative business outcomes
|
|
24
|
+
to-be/kpis.md # numeric: one row per KPI — AS-IS baseline, target, acceptance signal, owner
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
**What marks this phase successful.** The case model is complete when four things hold. Every `to-be/stages/<stage-id>.md` page carries both a stage type (`primary`/`secondary`) and a status (`confirmed`/`needs confirmation`/`excluded`). Every task on every stage page names its `Case task type`. Every stage subgraph in `to-be/diagram.md` has a matching stage page — a box with no page behind it is a drawing, not a design. And on existing work the current state is cased too, as `as-is/stages.md` plus a page per stage it lists; net-new work is not expected to have one. An excluded stage keeps its own page with its reason and counts as captured, never as drift. The case map itself carries a node per stage and per task the pages define.
|
|
28
|
+
|
|
29
|
+
## Entry Guard
|
|
30
|
+
|
|
31
|
+
If this is Existing + Case and neither `as-is/process.bpmn`, canonical `as-is/diagram.md`, nor legacy `as-is/overview.md` contains a user-confirmed current process map, refuse entry in business terms: *"Let's finish the current process first so the future design has a stable baseline."*
|
|
32
|
+
|
|
33
|
+
If this is New + Case, begin here and record in `to-be/case-details.md` that this is a net-new case capability with no current-state process. The PDD Current State section uses that fact to say AS-IS is not applicable. Do not create fake AS-IS detail.
|
|
34
|
+
|
|
35
|
+
For net-new Case, capture the case object, lifecycle, stages, owners, stage work, decisions, exceptions, evidence, systems, SLAs, and terminal outcomes using `interview-spine.md`. Carry the proposed stage/route shape into the Future Process Review; do not add a stage/route checkpoint. Do not compensate for missing stages, routes, owners, terminal outcomes, or exception handling with generic case language.
|
|
36
|
+
|
|
37
|
+
## Move 1 — Pre-read AS-IS case baseline
|
|
38
|
+
|
|
39
|
+
For Existing + Case, read `as-is/process.bpmn` when present, canonical `as-is/diagram.md` when present, `as-is/overview.md`, `as-is/stages.md` and `as-is/stages/` when present (the current-state stage model), `as-is/steps/`, `as-is/scheduling-and-triggers.md`, `as-is/data-inputs-outputs.md`, `as-is/exception-handling.md`, `as-is/pain-points.md`, `entities/applications/`, `entities/people/`, and any `to-be/seeds.md` created during AS-IS.
|
|
40
|
+
|
|
41
|
+
Normalize AS-IS into case dimensions:
|
|
42
|
+
- current trigger
|
|
43
|
+
- current stages
|
|
44
|
+
- current stage work / case activities
|
|
45
|
+
- stage owners / personas
|
|
46
|
+
- systems touched
|
|
47
|
+
- data, artifacts, and evidence
|
|
48
|
+
- decisions and routes
|
|
49
|
+
- exceptions, rework, and escalations
|
|
50
|
+
- volume / frequency / backlog
|
|
51
|
+
- cycle time / SLA
|
|
52
|
+
- AS-IS gaps and pain points
|
|
53
|
+
|
|
54
|
+
Convert the baseline into a target-change proposal table. Write `to-be/transformation-decisions.md` with columns: `AS-IS area | AS-IS issue | Proposed target change | User decision | Notes`.
|
|
55
|
+
|
|
56
|
+
Propose target changes from the AS-IS gaps and pain points, informed by Process Knowledge's target-state suggestions and your own domain knowledge of what's typically improved or automated for this kind of stage — not only what the user already named as a pain point. Present them inside the Future Process Review as "Proposed changes from today's process" — one confirmation covers the changes and the map together; do not run a separate target-change confirmation round. If a proposed change is genuinely uncertain and shape-defining, it joins the batched blocking questions.
|
|
57
|
+
|
|
58
|
+
For New + Case, skip AS-IS normalization and start with the Progressive case workshop below.
|
|
59
|
+
|
|
60
|
+
## Progressive Process Knowledge During TO-BE
|
|
61
|
+
|
|
62
|
+
Latched run first (SKILL.md, The latch): `{WikiPath}/research-pass.md` records `Process Knowledge state:` `closed` or `opted-out` → make none of the calls below, log `Phase: TO-BE — skipped` once in `process-knowledge.md`, and this phase's checkpoint is complete. Never send a decision to unlock them.
|
|
63
|
+
|
|
64
|
+
Use Process Knowledge for case lifecycle design suggestions: likely stages, case activities, evidence, controls, SLA patterns, exception stages, and UiPath case-work patterns. Confirmed user facts and wiki content remain the source of truth.
|
|
65
|
+
|
|
66
|
+
Call it at these TO-BE checkpoints:
|
|
67
|
+
|
|
68
|
+
1. **Before Move 2 case workshop.** Include matched process display names, current AS-IS summary when present, the case object or process goal, systems, participants, and known constraints. For New + Case, ask for likely case stages, stage work, decisions, evidence, controls, SLAs, and exception patterns. For Existing + Case, the stage list is already AS-IS's — ask instead for target-state best practices and automation patterns for those confirmed stages, not for stages to exist.
|
|
69
|
+
2. **After drafting target changes for Existing + Case, or after the first stage/lifecycle sketch for New + Case.** Include the proposed stages and decisions. Ask only whether the stage list itself is complete and correctly shaped — missing stages, wrong ordering, missing routing gates between stages. Task-level detail for each stage is checkpoint 4's job, not this one.
|
|
70
|
+
3. **Before writing the case map.** Ask for a target-state completeness check: missing stages, terminal outcomes, rework loops, exception paths, timers, handoffs, audit evidence, monitoring, and fallback paths.
|
|
71
|
+
4. **Before drafting each stage's detailed page in Move 4.** One call per stage, not one call for all of them — scope `Need now` to that single stage's name and ask for its complete task list, inputs/outputs, evidence, work types, and controls. A call covering "the proposed stages" or "the overall lifecycle" is checkpoint 2 or 3's job, not this one — the response is too size-capped to return real detail for more than one stage at a time.
|
|
72
|
+
5. **Before PDD readiness.** Ask for PDD-facing terminology, KPIs, controls, glossary terms, exception language, and any residual completeness gaps.
|
|
73
|
+
|
|
74
|
+
For follow-up calls, keep the same API shape and put the context into the `description`:
|
|
75
|
+
|
|
76
|
+
```text
|
|
77
|
+
Continue using these matched process references: <display names from process-knowledge.md>.
|
|
78
|
+
Confirmed current process: <brief AS-IS summary, or net-new with no AS-IS>.
|
|
79
|
+
Proposed future case design so far: <stage/lifecycle summary, decisions, systems, evidence>.
|
|
80
|
+
Need now: the complete task list, inputs/outputs, evidence, and controls for <one stage name> — not the whole case.
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
When using returned best practices, turn them into confirm-or-change options. Do not write a reference stage, control, SLA, or exception into `to-be/` unless it fits the user's scope and has been confirmed or recorded as an explicit assumption/open item.
|
|
84
|
+
|
|
85
|
+
Phase gate: follow the Gate's fit judgment (SKILL.md) for whether to call again here, never while the latch holds. When you do, append to `process-knowledge.md` a new entry with `Phase: TO-BE` and the result status before presenting case stages, target changes, a future-state design, a case map, or writing `to-be/` files. If the call errors, retry once; if the retry also errors, record the error in `process-knowledge.md` and ask the user whether to continue from confirmed AS-IS/source facts.
|
|
86
|
+
|
|
87
|
+
## Move 2 — Progressive case workshop
|
|
88
|
+
|
|
89
|
+
Listen first. Ask the user to describe the case in business terms: what starts it, what business object is being managed, which stages it moves through, who works it, what systems are involved, and how it closes.
|
|
90
|
+
|
|
91
|
+
Sketch privately. Infer the case shape from what the user said and from AS-IS if present, then ask anchored confirm-or-change questions. Do not ask a cold questionnaire; show what you think you have, then ask the smallest next question.
|
|
92
|
+
|
|
93
|
+
Run this progressive case workshop in order:
|
|
94
|
+
|
|
95
|
+
| # | Dimension | When to ask | What to capture |
|
|
96
|
+
|---|---|---|---|
|
|
97
|
+
| 1 | case objective and lifecycle | Opening TO-BE context | Business object, purpose, target outcome |
|
|
98
|
+
| 2 | Stage flow | shape-defining questions before the map | primary and secondary stages from start to finish, including supporting, rework, or exception paths; per stage: required for case completion?; per secondary stage: does it pause the main work (interrupting), what activates it (a decision outcome, a person choosing it, an outside event, a missed deadline), and does the case return to where it left off or end |
|
|
99
|
+
| 3 | Stage work / case activities | shape-defining questions before the map | What work happens in each stage, who or what does it, required completion, proposed Case task type; activation within the stage (in order, side by side, on demand, or on an event), whether it runs only once, and any skip condition |
|
|
100
|
+
| 4 | Systems and integrations | shape-defining questions before the map | systems per stage work/case activity, source of truth, read/write access, API, connector, UI, file, or email |
|
|
101
|
+
| 5 | Personas and owners | shape-defining questions before the map | Stage owners, case activity owners, reviewers, approvers, requesters; per persona, what they see and do when they open the case |
|
|
102
|
+
| 6 | Decisions and gates | shape-defining questions before the map | decision outcomes and routes, including advance, reject, request info, rework |
|
|
103
|
+
| 7 | Trigger and exit | shape-defining questions before the map | trigger or start condition — typed: someone creates it manually, a schedule, or an event in another system (and which); terminal outcomes, what "done" means |
|
|
104
|
+
| 8 | Exceptions and escalations | shape-defining questions before the map | exception stages, trigger source, recovery path, terminal failure path |
|
|
105
|
+
| 9 | Data, artifacts, and evidence | detail questions after the map | Inputs, outputs, attachments, evidence retained, fields driving decisions |
|
|
106
|
+
| 10 | SLA and timing | detail questions after the map | Case SLA, stage SLA, timers; per SLA: the at-risk warning point and the response — notify someone (whom) or change course into a stage |
|
|
107
|
+
| 11 | Volume / backlog | detail questions after the map | Case volume, backlog, peaks, aging risk, capacity pressure |
|
|
108
|
+
| 12 | Compliance and policy | detail questions after the map | Policy constraints, regulated approvals, audit evidence |
|
|
109
|
+
|
|
110
|
+
Rows 2, 3, 4, 6, 7, and 8 define the case shape. Do not skip them unless AS-IS or user-provided documents captured the answer verbatim and you have reflected it back for confirmation.
|
|
111
|
+
|
|
112
|
+
Primary and secondary stages are the only stage types. Primary stages are the main lifecycle; secondary stages support, rework, exception, or side-path work. Capture stages and exception stages as primary or secondary entries. Capture every user-provided/requested stage as its own `to-be/stages/<stage-id>.md` page before the map, even when the stage is excluded from the final design — write just enough to draw the map (name, type, status, required-for-completion, activated-by/on-leave for secondary stages, entry/exit criteria, and its case work/tasks per the Case task type checkpoint below — the map needs a node per task, not just per stage); Move 4 enriches the same page, it never becomes a second file.
|
|
113
|
+
|
|
114
|
+
Default to ask for shape-changing fields: trigger type, case exit, case activity owner/work pattern when the verb is ambiguous, decision route, exception trigger source, source of truth, and read/write access. Optional detail can be marked as an open question for the PDD, but shape-changing fields must be confirmed before the map.
|
|
115
|
+
|
|
116
|
+
Use solution-ready detail without naming downstream tools. The SDD phase derives implementation detail from the confirmed PDD and TO-BE sources, so the TO-BE must be concrete enough for a reader to understand the case structure. This guide produces the Case TO-BE design; PDD and SDD generation happen in their later phases.
|
|
117
|
+
|
|
118
|
+
When the future case introduces, changes, removes, or automates a business rule, write it to `to-be/business-rules.md`. Preserve AS-IS rule IDs when overriding an existing rule; assign new sequential BR IDs only for genuinely new future-state rules. Include the rule, where it is enforced, evidence retained, and whether it is confirmed or an open decision. State any confidence or quality threshold numerically (e.g. "DU confidence < 0.88 → halt and route to re-scan"), never as vague language like "low confidence."
|
|
119
|
+
|
|
120
|
+
Before generating the PDD, run a completeness check: unresolved shape decisions, missing systems/source-of-truth answers, missing decision routes, missing exception handling, unknown terminal outcomes, and unrecorded future-state business rules must either be answered or recorded as explicit open questions.
|
|
121
|
+
|
|
122
|
+
### Case task type checkpoint
|
|
123
|
+
|
|
124
|
+
For each stage activity, capture the product-facing case task that downstream tooling will later map. User-facing prompts can say "case activity", but that stage's `to-be/stages/<stage-id>.md` page must record `Case task` and `Case task type` in its own case-work section.
|
|
125
|
+
|
|
126
|
+
Supported Case task types:
|
|
127
|
+
- `process` — deployed orchestration process
|
|
128
|
+
- `agent` — UiPath agent reasoning over content or context
|
|
129
|
+
- `rpa` — deterministic UI automation / existing RPA process
|
|
130
|
+
- `action` — human-in-the-loop action, review, decision, approval, or sign-off
|
|
131
|
+
- `api-workflow` — coded/API workflow
|
|
132
|
+
- `case-management` — child case
|
|
133
|
+
- `execute-connector-activity` — one Integration Service connector operation
|
|
134
|
+
- `wait-for-connector` — wait for an external connector event/callback
|
|
135
|
+
- `wait-for-timer` — wait for time or a scheduled point
|
|
136
|
+
|
|
137
|
+
Do not use unsupported PO.Frontend-only task types in the BA PDD: `external-agent`, `external-workflow`, `document-extraction`, `function`, or `flow-process`. PO.Frontend may type them, but the downstream Maestro Case skill does not support them yet.
|
|
138
|
+
|
|
139
|
+
Ask when the type changes the case shape: approval/review/decide can be `action` or `agent`; SaaS calls can be `execute-connector-activity` or `api-workflow`; legacy UI work can be `rpa` or `process`; waits can be `wait-for-connector` or `wait-for-timer`. Compliance-driven sign-off forces `action` unless the user explicitly changes the business requirement.
|
|
140
|
+
|
|
141
|
+
Pick the type from what the task actually requires — system access, decision complexity, judgment involved — not from what's easiest to type. Ground it in Process Knowledge's automation patterns and your own domain knowledge of what's typically automated for this kind of task; `action` is a real answer when judgment genuinely can't be automated, never a default for when you're unsure. Ask a specific question whenever a task's type is genuinely unclear, even if it wouldn't change the overall case shape — correctness on this field is worth a question.
|
|
142
|
+
|
|
143
|
+
Capture each task's **activation** alongside its type — does it run in order after the previous task, side by side with others, on demand when a worker chooses it, or when an outside event arrives — plus whether it runs only once and any condition under which it is skipped. Downstream case tooling models these directly (sequential / parallel / ad-hoc / event-triggered, run-once, skip condition); best-assume from the described work and disclose in the stage's page.
|
|
144
|
+
|
|
145
|
+
Record task names exactly as the user describes them or as Process Knowledge returns them — never paraphrase or generalize a task name into a broader category (keep "3-way PO match against receiving log" as stated, don't compress it to "verify PO"). When a stage's work is still generic or thin, call Process Knowledge scoped to that one stage (`Need now: the complete task/step list for <stage>`, per the Gate) before finalizing its task list, and turn what comes back into confirm-or-change options — never write an unconfirmed task as fact. While the latch holds, make no such call: build the stage's task list from domain knowledge alone, as the same confirm-or-change options.
|
|
146
|
+
|
|
147
|
+
**A stage with one task is almost always under-captured.** Real case stages typically carry several distinct tasks, not a single headline activity — a request-intake stage alone can easily be seven: receive the request, verify eligibility, check the authorization requirement, verify the provider network, request missing documentation, classify urgency, and assign to a queue. Before closing out a stage's task list, ask whether one task genuinely covers everything that happens there, or whether you stopped after the first, most obvious step — this applies whether the tasks came from Process Knowledge or your own domain knowledge.
|
|
148
|
+
|
|
149
|
+
## Move 3 — Synchronize the Case Shape, Then Draft the Map
|
|
150
|
+
|
|
151
|
+
Draft the framing prose in `to-be/overview.md` and wait for the write result. Make the next mutation one `project-task-list` update of every affected ANALYSIS row in `TaskListPath`, including rows backed by earlier case-shape pages, with the intended answers, provenance, and statuses. Do not write the case map while any affected ANALYSIS row is stale.
|
|
152
|
+
|
|
153
|
+
After the synchronization gate succeeds, write the case map in `to-be/diagram.md` before drafting the remaining detailed pages — authored per the `case-design` family contract in `diagram-authoring.md` (stage-table-first authoring, dialect rules, semantic classes, and the case source audit all live there; the confirmed `to-be/stages/` pages are the table). It is `diagramFamily=case-design`, `flowchart LR`, with stage subgraphs, exactly one `case-task-*` per task, `case-ends-case` terminal markers, and no authored `classDef`. Complete the case source audit before the Future Process Review. Do not present the map or draft the detailed pages until the audit passes. Then run this phase's one self-review, before the review and never after it (SKILL.md "One Review Per Phase"): one pass, one fix round, and whatever it still leaves goes into **Assumptions and open gaps** — never a second pass. Every confirmed primary or secondary stage must appear in the case map as a stage subgraph. Excluded stages stay as their own `to-be/stages/<stage-id>.md` page with `Status: excluded` and the reason, and do not appear in the map. Sequence detail inside a stage lives in that stage's `to-be/stages/<stage-id>.md` page, not in intra-stage edges.
|
|
154
|
+
|
|
155
|
+
**Close this phase on its output.** Before presenting the review, run the readiness check as the
|
|
156
|
+
last silent step — it lists what is still unwritten, and a review presented with the
|
|
157
|
+
pages missing has closed nothing:
|
|
158
|
+
|
|
159
|
+
```
|
|
160
|
+
bash "{BusinessAnalysisSkillDir}/scripts/check-phase-ready.sh" --wiki "{WikiPath}" --phase to-be --route case
|
|
161
|
+
```
|
|
162
|
+
|
|
163
|
+
On Windows:
|
|
164
|
+
|
|
165
|
+
```
|
|
166
|
+
& "{BusinessAnalysisSkillDir}\scripts\check-phase-ready.ps1" -Wiki "{WikiPath}" -Phase to-be -Route case
|
|
167
|
+
```
|
|
168
|
+
|
|
169
|
+
`PHASEREADY:ok` is the only result that closes the phase. On `PHASEREADY:not-ready`,
|
|
170
|
+
write the pages and columns it names from the facts you have already confirmed, then
|
|
171
|
+
run it again. It never writes anything, so re-running it is free, and it fails open
|
|
172
|
+
with `PHASEREADY:skipped` if it cannot resolve the wiki — which is not a pass.
|
|
173
|
+
|
|
174
|
+
Closing sequence — do all, in order, silently until step 3:
|
|
175
|
+
|
|
176
|
+
1. Run the readiness check above and clear it to `PHASEREADY:ok`, writing any page it names from facts already confirmed. A review sent before this has closed nothing, and the phase ends at step 2 whether or not the pages exist.
|
|
177
|
+
2. Record this phase's Process Knowledge checkpoint in `process-knowledge.md` — its phase, focus and result status — for every retrieval the phase made, including the ones that matched nothing. A call whose result was never written down is not a checkpoint, and the next session reads the file, not this conversation: an unrecorded retrieval is one the project has to make again.
|
|
178
|
+
3. **MANDATORY STOP — Future Process Review (the phase checkpoint).** Render the complete review body as normal assistant Markdown immediately before one AskUser call in the same turn. Use these fixed headings: **Future case**, **Stages and ownership**, **Routes and terminal outcomes**, **Proposed changes from today's process** (existing work only), and **Assumptions and open gaps**. The validated diagram (the Case map) is already visible beside this quick-glance review. Never compress the review into the AskUser `intro` or `question`; a short "map ready" recap is not the Future Process Review. AskUser contains only the final decision: *"Confirm / Change / Attach or record more evidence?"* Do not draft detailed pages while the canonical diagram is missing or fails the audit. A diagram-only correction needs another task list mutation only when it changes a business fact; in that case update the supporting factual page and pass the synchronization gate before presenting it. Once the user confirms the case map, stamp `verified` on the confirmed `to-be/` pages per SKILL.md Page Trust Stamps, and call `AskUserFeedback` with `checkpoint: 'ba.toBeCreated'` (one non-blocking call; do not announce it or wait for a rating; skip silently if the tool is unavailable).
|
|
179
|
+
|
|
180
|
+
## Move 4 — Draft Case Detail
|
|
181
|
+
|
|
182
|
+
After map confirmation, draft the rest of the `to-be/` folder:
|
|
183
|
+
|
|
184
|
+
- `to-be/case-details.md` — case objective and lifecycle, trigger or start condition, terminal outcomes.
|
|
185
|
+
- `to-be/transformation-decisions.md` — Existing + Case only; AS-IS issue, proposed target change, user decision, notes.
|
|
186
|
+
- `to-be/stages/<stage-id>.md` — one page per stage, whether it's in the confirmed map or excluded from it; this is the sole source per stage, no separate ledger. File name = the stage's subgraph id in `to-be/diagram.md` for a mapped stage (rename a stage by changing its quoted title, keep the id), or a stable slug for an excluded one. Each page carries: stage type (`primary` or `secondary`); status (confirmed / needs confirmation / excluded, with a reason if excluded); source (user / document / Process Knowledge); purpose; required for case completion; interrupting (a property of the entry condition, on any stage; a secondary stage's entry is always interrupting); activated-by (a decision outcome / user-selected / external event / SLA breach); on-leave behavior (return to the interrupted work, wait for the user to choose, or exit only); entry criteria and flows from; exit criteria, routes, and flows to; case work in this stage as its own task table — Case task, Case task type, owner, work pattern, activation (in order / side by side / on demand / on event), run-once, skip-when, system, input, output, required completion, entry condition, evidence produced; owners and personas; systems and source of truth; inputs and outputs; SLA (target, at-risk point, response); key decision; exceptions and rework paths opened from here; evidence produced. A stage that exists only as a map box is not designed; PDD §4.2.1 renders one block per stage from these pages.
|
|
187
|
+
- `to-be/decisions-and-routes.md` — decision outcomes and routes, including rework loops and terminal outcomes.
|
|
188
|
+
- `to-be/data-and-evidence.md` — data, artifacts, and evidence needed to open, route, decide, complete, audit, and retain the case.
|
|
189
|
+
- `to-be/business-rules.md` — new, changed, removed, or automated rules; include enforcement point, evidence retained, and confirmation status.
|
|
190
|
+
- `to-be/exception-handling.md` — exception stages, triggers, owner, recovery path, terminal failure path.
|
|
191
|
+
- `to-be/slas.md` — SLA and timing by stage and case activity; include timers, the at-risk warning point, and the response per SLA (notify whom, or change course into which stage).
|
|
192
|
+
- `to-be/personas.md` — personas and owners, including requester, case owner, reviewers, approvers, and system personas; one line per persona on what they see and do when they open the case (feeds the solution design's app views).
|
|
193
|
+
- `to-be/benefits.md` — qualitative business outcomes only; no ROI math.
|
|
194
|
+
- `to-be/kpis.md` — the numeric artifact, one row per KPI: `KPI | AS-IS baseline (value + measurement method) | Target | Acceptance signal | Owner`. Carry each baseline figure verbatim from `as-is/metrics.md` with the measurement method beside it, and each target verbatim from the confirmed target discussion — never recompute, round, or derive either one. On net-new work there is no baseline: write `no current baseline (net-new)` in that cell and keep the target, the acceptance signal and the owner. Where a target was never discussed, keep the row with its baseline filled and write the target as a concrete open question rather than dropping the KPI. This file is where every number the document quotes as a target comes from: `benefits.md` stays qualitative, and a qualitative page cannot source PDD §1.2's baseline-and-target pair or §10's target table.
|
|
195
|
+
|
|
196
|
+
Append any new open items or carried assumptions from this phase to `queries/open-questions.md`. After each completed factual write round, make task list synchronization the next mutation before continuing with another write round or user-facing recap. Update `{WikiPath}/index.md` only after the detail pages and their task list synchronization boundaries are complete. When confirmation changes a row's status, update `task-list.md` before advancing. Drafting these pages is free; changing a fact on a page the map confirmation stamped `verified` is named in chat, in the same reply that makes it (SKILL.md "Editing a confirmed page").
|
|
197
|
+
|
|
198
|
+
## Detail Quality Bar
|
|
199
|
+
|
|
200
|
+
The Case TO-BE must be specific enough for PDD Section 4 to describe:
|
|
201
|
+
|
|
202
|
+
- the business object being managed, its identifier, and the states it moves through;
|
|
203
|
+
- the full lifecycle from trigger through terminal outcomes, with each terminal outcome named;
|
|
204
|
+
- case stages and case activities, including exception stages;
|
|
205
|
+
- per case task: its `Case task type`, its work pattern, how it is activated, the system(s) it runs in, and a description a builder could implement from — a task row that names only a title is not a designed task;
|
|
206
|
+
- case-level detail the stages hang off: the trigger type (manual, scheduled, external event), who can open the case, the retention or closure rule, and any case-wide constraint that is not stage-specific;
|
|
207
|
+
- one `to-be/stages/<stage-id>.md` page per stage in the confirmed map, plus one per excluded stage with its exclusion reason — no mapped stage without a page, no page silently orphaned from the map without an excluded status;
|
|
208
|
+
- more than one task in a stage's task table, unless that stage is genuinely a single atomic activity — before generating the PDD, re-check every stage with exactly one task; a lone task is a signal to look for more, not a stopping point;
|
|
209
|
+
- task types that actually vary with what each task requires — if most or all tasks are typed `action`, that's a signal the automation question was never really asked; re-examine each one against Process Knowledge and domain knowledge before finalizing;
|
|
210
|
+
- for Existing + Case, at least one stage or task that genuinely changed mode, owner, or automation from AS-IS — a TO-BE where every stage is identical to AS-IS with new labels is not a future-state design;
|
|
211
|
+
- stage owners and case activity owners;
|
|
212
|
+
- required data, artifacts, and evidence;
|
|
213
|
+
- decision outcomes and routes;
|
|
214
|
+
- SLA and timing constraints, including at-risk points and responses;
|
|
215
|
+
- volume / backlog constraints;
|
|
216
|
+
- exception handling, rework, and terminal failure handling;
|
|
217
|
+
- the typed trigger, stage activation sources, interrupting behavior, and task activation order — the fields downstream case tooling models directly.
|
|
218
|
+
|
|
219
|
+
If any of these are unknown, ask before generating the PDD or mark the item as a concrete open question. Do not fill gaps with generic case language.
|
|
220
|
+
|
|
221
|
+
## Closing Phase 2
|
|
222
|
+
|
|
223
|
+
The Future Process Review confirmation closes the phase. State in one line that the process document can be generated whenever they're ready — the first ```sf chip carries `Generate the process document`. Do not ask an additional "generate now?" question; enter Phase 3 only on the user's explicit request. Do not generate `sdd.md` here; after PDD generation, continue to Handoff.
|