@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,215 @@
|
|
|
1
|
+
# Diagram Authoring — Mermaid Maps
|
|
2
|
+
|
|
3
|
+
Read once per session before authoring, regenerating, refining, or repairing any diagram.
|
|
4
|
+
|
|
5
|
+
**What a process map is for.** A map is a confirmation surface a business user reads in five seconds in a narrow, tall side panel — not process documentation. The map shows the shape (sequence, decisions, exceptions, terminal outcomes); the semantic classes carry everything else (the renderer turns them into colors, badges, and icons); timers, SLAs, retry counts, rules, and open questions live in the wiki pages, never in the map.
|
|
6
|
+
|
|
7
|
+
**Level: activities, never clicks.** One node per sub-process or activity, about 12–20 nodes. UI-level steps (clicks, fields, screens) never go in the map, even when the user asks for them; they live in the step pages, and on a current-process map each node opens them through the evidence sidecar (below). When the user asks to see clicks or screens in the map, answer in one plain sentence and leave the map as it is: "The map stays at activity level so it reads at a glance — click any activity to open its step-by-step table."
|
|
8
|
+
|
|
9
|
+
**This guide is phase-free.** The phase guide that sent you here owns which file to write and which family it uses; this guide owns only how to author each family correctly. In particular: the wiki folder a map lives in carries current-vs-future — a class never does. There is no `mode-current` or `mode-future`; `mode-*` states how a step runs in whichever state the map documents, and every mode on a future-state map is a decision the user confirmed, never a guess.
|
|
10
|
+
|
|
11
|
+
## Families
|
|
12
|
+
|
|
13
|
+
| Family | Form | Orientation | Template |
|
|
14
|
+
|---|---|---|---|
|
|
15
|
+
| `generic` | Mermaid flowchart — step sequence with decisions and modes | `flowchart TB` | below |
|
|
16
|
+
| `case-design` | Mermaid stage map — work grouped in owned stages | `flowchart LR` | below + stage semantics in `case-to-be-design.md` |
|
|
17
|
+
| BPMN | BPMN 2.0 semantic XML — Delegate lays it out deterministically | n/a | profile + validation in `bpmn-to-be-design.md`; no Mermaid authored |
|
|
18
|
+
|
|
19
|
+
A `diagram.md` contains ONLY one complete fenced Mermaid block with the family on the opening fence — no frontmatter, headings, or prose; framing prose stays in `overview.md`.
|
|
20
|
+
|
|
21
|
+
## Non-negotiable generation gate
|
|
22
|
+
|
|
23
|
+
The user must receive a supported rich diagram, not a Prepare / Repair warning surface. A WriteFile or EditFile success is not a stopping point and is never evidence that the diagram renders. The next tool call after every canonical diagram write or edit must be the platform lint command from "Diagram source audit" below. Do not reason that lint is unnecessary or skip it because the source looks plausible. Do not send any user-facing message or AskUser checkpoint before `DIAGRAMLINT:ok`. If lint fails, keep the work internal: repair the canonical file and lint again. This gate applies to both Mermaid families; BPMN uses its own mandatory saved-artifact validator. It applies identically on a refinement turn: a map redrawn because a fact changed is validated exactly like a new one.
|
|
24
|
+
|
|
25
|
+
## How to author
|
|
26
|
+
|
|
27
|
+
Copy the matching template and adapt it. Author in this exact order — it is also the shape the lint checks:
|
|
28
|
+
|
|
29
|
+
1. the fence with the family;
|
|
30
|
+
2. one flowchart declaration;
|
|
31
|
+
3. every node, one per line, declared before any edge uses it;
|
|
32
|
+
4. every edge, one per line;
|
|
33
|
+
5. exactly one `class` line per node.
|
|
34
|
+
|
|
35
|
+
Then run the lint (below) and fix until it passes.
|
|
36
|
+
|
|
37
|
+
### `generic` family template
|
|
38
|
+
|
|
39
|
+
```mermaid diagramFamily=generic
|
|
40
|
+
flowchart TB
|
|
41
|
+
received(("Invoice received"))
|
|
42
|
+
checkInvoice{"Invoice valid?"}
|
|
43
|
+
fixInvoice["Request correction from vendor"]
|
|
44
|
+
matchPo["Match invoice to purchase order"]
|
|
45
|
+
approveInvoice["Approve for payment"]
|
|
46
|
+
waitFunds["Wait for payment run"]
|
|
47
|
+
postPayment["Post payment in ledger"]
|
|
48
|
+
paid(("Invoice paid"))
|
|
49
|
+
received --> checkInvoice
|
|
50
|
+
checkInvoice -->|Valid| matchPo
|
|
51
|
+
checkInvoice -->|Invalid| fixInvoice
|
|
52
|
+
fixInvoice --> checkInvoice
|
|
53
|
+
matchPo --> approveInvoice
|
|
54
|
+
approveInvoice --> waitFunds
|
|
55
|
+
waitFunds --> postPayment
|
|
56
|
+
postPayment --> paid
|
|
57
|
+
class received kind-event,mode-manual,icon-play
|
|
58
|
+
class checkInvoice kind-decision,mode-automated,system-sap
|
|
59
|
+
class fixInvoice kind-task,mode-manual,owner-finance,icon-mail
|
|
60
|
+
class matchPo kind-task,mode-automated,system-sap
|
|
61
|
+
class approveInvoice kind-task,mode-review,owner-finance,icon-user-check
|
|
62
|
+
class waitFunds kind-wait,mode-automated
|
|
63
|
+
class postPayment kind-task,mode-automated,system-sap
|
|
64
|
+
class paid kind-event,mode-automated,icon-target
|
|
65
|
+
```
|
|
66
|
+
|
|
67
|
+
Rules the template embodies:
|
|
68
|
+
|
|
69
|
+
- Node IDs: unique ID matching `[A-Za-z][A-Za-z0-9_]*`. Never a Mermaid keyword — above all never lowercase `end` (it closes subgraphs and kills the parser; use `endNode`, `paid`, `orderShipped`).
|
|
70
|
+
- Declare every node exactly once before the edges that reference it. One node or one edge per line — no chained `a --> b --> c`, no `&` shortcuts.
|
|
71
|
+
- Labels: double-quoted inside the shape, single-line plain text, at most ~6 words, verb + object. No HTML (`<br/>` is the classic mistake), no Markdown, no system names or timings in labels — classes and pages carry those.
|
|
72
|
+
- Shapes: `["Task"]`, `{"Decision?"}`, `(("Event"))` — nothing else (no stadiums `([ ])`, no cylinders).
|
|
73
|
+
- Edges: `-->` or labeled `-->|Outcome|`. Label every decision branch.
|
|
74
|
+
- Gateways from the decision table: each condition is a `kind-decision` node with every outcome labelled; distinct outcomes are distinct nodes. Independent parallel work (AND) is one node with two outgoing edges, each labelled `In parallel`, rejoining at one node where the work converges; never an exclusive decision.
|
|
75
|
+
- Classes: assign exactly one explicit `class` statement to every node. Each `generic` node gets exactly one `kind-*` and exactly one `mode-*`, plus `owner-*`/`system-*`/`icon-*` when known. Never use `:::className` shorthand. Attach classes only through explicit `class` statements — never chained `:::a:::b`, which is a parse error.
|
|
76
|
+
- Layout: `flowchart TB` only; keep the main path vertical, put exceptions and rework in short side branches that reconnect near the step they leave (like `fixInvoice` above); at most ~20 nodes (Level above) and three sibling branches — collapse bigger fan-outs into one sub-process node; its steps stay in the step pages at the source's full granularity, never uncaptured.
|
|
77
|
+
|
|
78
|
+
### Class vocabulary (anything else is rejected as unknown)
|
|
79
|
+
|
|
80
|
+
| Prefix | Values |
|
|
81
|
+
|---|---|
|
|
82
|
+
| `kind-` | `task`, `decision`, `event`, `wait`, `subprocess`, `control`, `evidence`, `data-store` |
|
|
83
|
+
| `mode-` | `automated`, `assisted`, `agent`, `review`, `manual` — how the step runs in the state this map documents. Never bare legacy aliases; never `attended` (an attended step is `mode-assisted`); never `mode-current`/`mode-future` (the file's folder carries that) |
|
|
84
|
+
| `owner-` / `system-` | lowercase-hyphen slug: `owner-finance`, `system-dynamics-crm` (`[a-z0-9]+(-[a-z0-9]+)*`) |
|
|
85
|
+
| `icon-<slug>` (optional) | action icon, e.g. `icon-play`, `icon-target`, `icon-mail`, `icon-user-check`, `icon-search`, `icon-bot`; an unknown slug falls back to the kind icon |
|
|
86
|
+
|
|
87
|
+
`owner-*`/`system-*` values must come from confirmed wiki facts — never invented to fill a required class slot.
|
|
88
|
+
|
|
89
|
+
### `case-design` family template
|
|
90
|
+
|
|
91
|
+
The opening fence is exactly `diagramFamily=case-design`; the declaration is exactly `flowchart LR`.
|
|
92
|
+
|
|
93
|
+
```mermaid diagramFamily=case-design
|
|
94
|
+
flowchart LR
|
|
95
|
+
caseStart(("Case submitted"))
|
|
96
|
+
|
|
97
|
+
subgraph intake["Intake"]
|
|
98
|
+
validate["Validate request"]
|
|
99
|
+
end
|
|
100
|
+
|
|
101
|
+
subgraph review["Review"]
|
|
102
|
+
assess["Assess case"]
|
|
103
|
+
end
|
|
104
|
+
|
|
105
|
+
subgraph exception["Exception handling"]
|
|
106
|
+
requestInfo["Request missing information"]
|
|
107
|
+
end
|
|
108
|
+
|
|
109
|
+
caseStart --> validate
|
|
110
|
+
validate -->|complete enough| assess
|
|
111
|
+
validate -. missing info .-> requestInfo
|
|
112
|
+
requestInfo -. resubmitted .-> validate
|
|
113
|
+
|
|
114
|
+
class caseStart kind-event
|
|
115
|
+
class validate kind-task,case-task-action,owner-operations,system-case-platform
|
|
116
|
+
class assess kind-task,case-task-agent,owner-case-owner,case-ends-case
|
|
117
|
+
class requestInfo kind-task,case-task-action,owner-requester
|
|
118
|
+
```
|
|
119
|
+
|
|
120
|
+
`case-design` intentionally uses `flowchart LR`: its specialized renderer presents case stages as horizontal progression. The `flowchart TB` narrow-panel rule for `generic` maps does not apply to this family.
|
|
121
|
+
|
|
122
|
+
**Author from a stage table, then transcribe.** Free-authoring case maps is the top failure source. Never invent a Case map directly from prose. Copy the Case template first, complete the table below with one row per work item, then transcribe the completed stage table mechanically:
|
|
123
|
+
|
|
124
|
+
| Stage | Owner | Work item | How it runs (`case-task-*`) | Routes to | Rework? |
|
|
125
|
+
|---|---|---|---|---|---|
|
|
126
|
+
|
|
127
|
+
Then transcribe mechanically: one `subgraph` per distinct Stage value (quoted label), one task node per Work item row, one `class` line per node using the table's type column, a solid labeled edge per Routes-to entry, a dashed `-. label .->` edge per Rework row. **Stages are subgraphs, never classes** — there is no `kind-stage`; a flat map with stage-named tags is wrong by construction.
|
|
128
|
+
|
|
129
|
+
Case rules on top of the shared subset:
|
|
130
|
+
|
|
131
|
+
- Give every node and subgraph a unique ID matching `[A-Za-z][A-Za-z0-9_]*`; subgraph labels double-quoted: `subgraph intake["Intake"]`.
|
|
132
|
+
- Case starts render from ungrouped `kind-event` nodes.
|
|
133
|
+
- Work steps / case tasks: `kind-task` plus exactly one supported `case-task-*` class (`process`, `agent`, `rpa`, `action`, `api-workflow`, `case-management`, `execute-connector-activity`, `wait-for-connector`, `wait-for-timer`).
|
|
134
|
+
- Branching outcomes: `kind-decision`. Timers or holds: `kind-wait`. Evidence or document capture: `kind-evidence`.
|
|
135
|
+
- Terminal outcomes are case exit rules, not Mermaid nodes. Do not draw standalone terminal outcome nodes. Use `case-ends-case` on the final case task in the stage whose completion is tied to a case exit/completion rule.
|
|
136
|
+
- Give every node exactly one explicit `class` statement and exactly one supported kind class. Work steps also get exactly one supported `case-task-*` class. Add only valid `owner-*`, `system-*`, and `case-ends-case` tokens where applicable.
|
|
137
|
+
- Do not use `kind-trigger` or `kind-case-outcome`. Do not use `mode-*` classes on case maps — the map shows stages, case activities, owners, systems, decisions, waits, evidence, and routes, never automation modes.
|
|
138
|
+
- Never emit `classDef` on case maps.
|
|
139
|
+
|
|
140
|
+
**Case source audit** (run on the canonical case map file, in addition to the lint): one complete Mermaid fence; one `flowchart LR` declaration; at least one stage `subgraph`, each closed by `end`; unique non-keyword node and subgraph IDs; every edge endpoint declared; exactly one class statement and one supported kind per node; exactly one `case-task-*` on each work step; no unknown classes, `mode-*`, `:::`, HTML, or styling directives.
|
|
141
|
+
|
|
142
|
+
Rich-view expectation: the case renderer draws stage-to-stage progression. Edges between two nodes inside the same stage subgraph are intentionally not drawn by the rich view — that is correct behavior, never something to repair; sequence detail inside a stage lives in the supporting work pages.
|
|
143
|
+
|
|
144
|
+
### classDef
|
|
145
|
+
|
|
146
|
+
Never author `classDef` — colors and semantics both come from the `class` statements; the renderer styles the rich view itself. When repairing an existing diagram that already carries `classDef` styling or non-semantic style classes, preserve them, but never treat a `classDef` declaration as a semantic assignment.
|
|
147
|
+
|
|
148
|
+
## What breaks rendering
|
|
149
|
+
|
|
150
|
+
The renderer parses with Mermaid, converts to a semantic graph, and classifies. These are the verdicts and their causes — the lint reports the same codes:
|
|
151
|
+
|
|
152
|
+
| Verdict | Cause |
|
|
153
|
+
|---|---|
|
|
154
|
+
| `invalid-syntax` | Mermaid parse error: lowercase `end` as an ID, chained `:::`, unquoted labels containing parentheses or pipes |
|
|
155
|
+
| `unsupported-diagram-type` | first line is not a flowchart declaration |
|
|
156
|
+
| `sparse-graph` | fewer than 2 nodes or 0 edges — a renderer minimum, **not** a statement about how big the design should be |
|
|
157
|
+
| `unresolved-endpoint` | duplicate node IDs, or an edge naming an undeclared node |
|
|
158
|
+
| `missing-semantics` | zero nodes carry any recognized class (styling-only classes) |
|
|
159
|
+
| `degraded-semantic-coverage` | some nodes unclassed — supported status requires 100% coverage |
|
|
160
|
+
| `unknown-classes` | any token outside the vocabulary above (`kind-activity`, `mode-attended`, uppercase slugs) |
|
|
161
|
+
| `conflicting-semantics` | two modes on one node, two case task types, kind contradicting the shape |
|
|
162
|
+
| `source-too-large` | fenced source over 10,000 characters — the map holds step-level detail; collapse to sub-process nodes (Size failures below) |
|
|
163
|
+
|
|
164
|
+
## Diagram source audit
|
|
165
|
+
|
|
166
|
+
After every write of a canonical `diagram.md`, **run the bundled lint against the saved file as the very next tool call** — never self-assess the source by eye and never stop at a successful WriteFile/EditFile result. Select the command from `PlatformContextType` `os.name`; the script directory is pre-resolved, substitute only the diagram path:
|
|
167
|
+
|
|
168
|
+
**macOS** (`ExecuteBashCommand`):
|
|
169
|
+
|
|
170
|
+
```bash
|
|
171
|
+
bash "{BusinessAnalysisSkillDir}/scripts/lint-diagram.sh" --file "<absolute-diagram-md-path>"
|
|
172
|
+
```
|
|
173
|
+
|
|
174
|
+
**Windows** (`ExecutePowershellCommand`):
|
|
175
|
+
|
|
176
|
+
```powershell
|
|
177
|
+
& "{BusinessAnalysisSkillDir}\scripts\lint-diagram.ps1" -File "<absolute-diagram-md-path>"
|
|
178
|
+
```
|
|
179
|
+
|
|
180
|
+
**How big the map should be.** The map has one node for every unit the pages behind it define — one per stage,
|
|
181
|
+
step, activity or route that exists on disk — and no node for anything they do not. There is no target count to
|
|
182
|
+
reach: the size is whatever the design is, and the lint reports `nodes=N edges=M` so you can check the drawing
|
|
183
|
+
against the pages, not against a number. A map that feels thin is a question about the pages, never about the
|
|
184
|
+
picture: go back and finish the pages, then redraw from them. Adding a box the pages do not contain is the one
|
|
185
|
+
response that makes the document worse.
|
|
186
|
+
|
|
187
|
+
Fix every `DIAGRAMLINT:error` in one edit pass, then re-run until `DIAGRAMLINT:ok`; resolve warnings whenever already touching the file. Budget: 2 lint runs per map — write, lint, fix everything reported, lint. Reaching for a third run means the source is being patched piecemeal: stop and rewrite it whole from the sub-process list. Do not present the map, advance the phase, or embed the fragment in a PDD while the lint fails. A successful file write alone does not make the map ready — only a passing lint does.
|
|
188
|
+
|
|
189
|
+
**Size failures** (`source-too-large`, `source-size`): the map is below activity level. Fix in one rewrite: regroup the nodes into sub-process nodes (Level above), file each dropped step under the node that now owns it (its step pages and sidecar note), re-key the sidecar to the surviving node ids, then lint once. Never shorten labels, drop words, or trim characters to get under the cap.
|
|
190
|
+
|
|
191
|
+
A passing lint is necessary, not sufficient: before presenting, confirm every branch, exception route, and terminal outcome on the map matches the corresponding confirmed wiki fact. A mismatch is not a question for the user — repair the diagram from the confirmed facts and re-validate silently before presenting; surface it only if the mismatch traces to a fact that is itself unconfirmed or conflicting.
|
|
192
|
+
|
|
193
|
+
If command execution is unavailable, verify the read-back source manually instead: one fence, one flowchart declaration, at least two nodes and one edge, unique non-keyword IDs, every edge endpoint declared, exactly one class statement per node with vocabulary classes only, no `:::`/HTML/`classDef` authored, under 10,000 characters.
|
|
194
|
+
|
|
195
|
+
## Evidence sidecar audit
|
|
196
|
+
|
|
197
|
+
On a `case-design` or `generic` map the same lint run also audits the sibling `attachments.md` — the evidence-and-notes sidecar. It is found next to the file you pass, so the command takes no extra argument. Evidence filed under a key nothing on the map answers to renders nothing and raises no error: a restructure that redraws the map without re-keying the sidecar silently orphans the evidence the user supplied. Both codes block:
|
|
198
|
+
|
|
199
|
+
| Code | Cause |
|
|
200
|
+
|---|---|
|
|
201
|
+
| `orphaned-attachment-key` | an `attachments:` key that is not a stage `subgraph` id, that stage's label slug, or a work item's node id (`generic`: not a node id) |
|
|
202
|
+
| `orphaned-note-key` | a `notes:` key that is none of those either |
|
|
203
|
+
|
|
204
|
+
Both maps take the same key spellings, so evidence and notes are filed per stage **or** per work item: a reference document that belongs to one task hangs off that task's node id, and the viewer offers it on the task itself. The `subgraph` id and the node id are the canonical spellings. A `generic` map has no stages — subgraphs there are not keys — so its sidecar is keyed by node id alone, and clicking a node opens its note and step pages.
|
|
205
|
+
|
|
206
|
+
The lint reports the offending key with its `attachments.md` line. Repair it by re-keying the entry to whatever now owns the evidence, never by deleting a ref the user supplied; a stage split means deciding which successor each ref belongs to. Only the sidecar's leading YAML frontmatter is read, exactly as the viewer reads it.
|
|
207
|
+
|
|
208
|
+
## User-dragged layout sidecar
|
|
209
|
+
|
|
210
|
+
A diagram may have a `<diagram>-positions.json` sibling recording where the user dragged nodes in the visual view. It is user-owned UI state: **never create, edit, or delete it**, and never mention it in a map. When revising a diagram, keep existing node ids for steps that survive the revision — each id keeps the user's dragged position for that step; renaming an id needlessly discards it.
|
|
211
|
+
|
|
212
|
+
## Legacy and repair situations
|
|
213
|
+
|
|
214
|
+
- **Legacy fallback.** Projects whose map still lives in `overview.md` stay readable; any create/regenerate/revision writes the canonical `diagram.md` only. Write and validate the canonical file first; only after it passes, remove the legacy Mermaid block (and obsolete `diagramFamily` field) from `overview.md`, preserving its prose. A failed canonical write leaves the legacy source untouched.
|
|
215
|
+
- **Host repair requests.** The diagram panel's Prepare / Repair / Revise actions send a message naming the file, the family, and machine reason codes (the verdicts above). Treat those reason codes as authoritative for that turn. Edit the named canonical file in place — exactly one fenced block, no sidecar or duplicate file, no diagram source pasted into chat — then re-run the lint.
|
|
@@ -0,0 +1,134 @@
|
|
|
1
|
+
# Industry Gap Reference
|
|
2
|
+
|
|
3
|
+
Industry-specific probes for the Phase 1 gap pass. Match the process to one or more sections below and pull the relevant gaps. If nothing matches closely, skip this file — `as-is-capture.md` covers universal gaps that apply to every process.
|
|
4
|
+
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
## Finance Ops — AR / Collections
|
|
8
|
+
|
|
9
|
+
Common gaps to probe:
|
|
10
|
+
- Credit limit checks and credit hold placement/release (SAP, Oracle, NetSuite)
|
|
11
|
+
- New invoice notification to customer — separate from dunning
|
|
12
|
+
- Promise-to-Pay (PTP) tracking and automated follow-up on missed PTPs
|
|
13
|
+
- Partial payment handling and residual balance treatment
|
|
14
|
+
- Dispute management workflow — who logs it, who resolves it, what pauses dunning
|
|
15
|
+
- Write-off / bad debt provisioning and approval thresholds
|
|
16
|
+
- Escalation to legal or external collections agency (90+ days)
|
|
17
|
+
- Deduction management — short payments with reason codes
|
|
18
|
+
- Cash application / payment matching — remittance advice processing
|
|
19
|
+
- Multi-entity / multi-currency and intercompany netting
|
|
20
|
+
- Customer master data quality — wrong contact, address, or payment terms
|
|
21
|
+
- Early payment discount (EPD) eligibility and automated application
|
|
22
|
+
- Direct debit / autopay setup and failure handling
|
|
23
|
+
- Self-service portal — invoice download, dispute submission, payment
|
|
24
|
+
- Month-end / quarter-end acceleration of collections (DSO pressure)
|
|
25
|
+
- Unapplied cash and on-account credit management
|
|
26
|
+
|
|
27
|
+
**Key metrics:** DSO, CEI (Collections Effectiveness Index), Aging Distribution, Bad Debt Ratio, PTP Kept Rate, Dispute Resolution Cycle Time, Cash Flow Forecast Accuracy.
|
|
28
|
+
|
|
29
|
+
---
|
|
30
|
+
|
|
31
|
+
## Finance Ops — AP / Purchase-to-Pay
|
|
32
|
+
|
|
33
|
+
Common gaps to probe:
|
|
34
|
+
- Invoice receipt channel — email, portal, EDI, paper scan
|
|
35
|
+
- 2-way / 3-way PO matching and tolerance rules
|
|
36
|
+
- Non-PO invoice approval workflow and delegation of authority
|
|
37
|
+
- Duplicate invoice detection
|
|
38
|
+
- Vendor statement reconciliation
|
|
39
|
+
- Early payment discount capture vs. standard payment run
|
|
40
|
+
- Blocked invoice handling — price, quantity, or quality discrepancies
|
|
41
|
+
- Vendor master data maintenance and bank account change controls
|
|
42
|
+
- Payment run approval and bank file generation
|
|
43
|
+
|
|
44
|
+
**Key metrics:** Invoice Processing Time, Touchless Rate, Duplicate Rate, On-Time Payment %, Discount Capture Rate, Cost per Invoice.
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
## HR — Onboarding / Offboarding
|
|
49
|
+
|
|
50
|
+
Common gaps to probe:
|
|
51
|
+
- Pre-boarding tasks — contract signing, background check, equipment provisioning
|
|
52
|
+
- System access provisioning / deprovisioning (AD, M365, SAP, Salesforce)
|
|
53
|
+
- Badge and physical access
|
|
54
|
+
- Mandatory training and compliance acknowledgements
|
|
55
|
+
- Equipment return and asset tracking on offboarding
|
|
56
|
+
- Final payroll, accrued leave payout, and severance
|
|
57
|
+
- Knowledge transfer and handover documentation
|
|
58
|
+
- Alumni portal access
|
|
59
|
+
|
|
60
|
+
**Key metrics:** Time-to-Productivity, Offboarding Completion Rate, Compliance Training Completion, System Access Deprovisioning Time.
|
|
61
|
+
|
|
62
|
+
---
|
|
63
|
+
|
|
64
|
+
## IT / ITSM — Incident / Change / Access
|
|
65
|
+
|
|
66
|
+
Common gaps to probe:
|
|
67
|
+
- Auto-classification and routing rules — CI, priority matrix
|
|
68
|
+
- SLA breach escalation path
|
|
69
|
+
- Major incident (P1/P2) bridge call and stakeholder comms
|
|
70
|
+
- Change Advisory Board (CAB) approval gates
|
|
71
|
+
- Rollback plan and post-change verification steps
|
|
72
|
+
- Access re-certification / periodic review
|
|
73
|
+
- Orphaned account detection
|
|
74
|
+
|
|
75
|
+
**Key metrics:** MTTR, First Call Resolution (FCR), Change Success Rate, SLA Compliance %, Reopen Rate.
|
|
76
|
+
|
|
77
|
+
---
|
|
78
|
+
|
|
79
|
+
## Supply Chain — Procurement / PO-to-Receipt
|
|
80
|
+
|
|
81
|
+
Common gaps to probe:
|
|
82
|
+
- Approved vendor list (AVL) check
|
|
83
|
+
- Sourcing event (RFQ/RFP) trigger threshold
|
|
84
|
+
- PO acknowledgement from vendor
|
|
85
|
+
- Partial delivery and goods receipt handling
|
|
86
|
+
- Quality inspection and non-conformance reporting
|
|
87
|
+
- Return to vendor (RTV) process
|
|
88
|
+
- Consignment stock and VMI arrangements
|
|
89
|
+
|
|
90
|
+
**Key metrics:** PO Cycle Time, On-Time Delivery, Supplier Lead Time Variance, Maverick Spend %, PO Accuracy.
|
|
91
|
+
|
|
92
|
+
---
|
|
93
|
+
|
|
94
|
+
## Sales — Quote-to-Cash
|
|
95
|
+
|
|
96
|
+
Common gaps to probe:
|
|
97
|
+
- Quote approval and discount authorisation matrix
|
|
98
|
+
- CPQ configuration rules and product compatibility checks
|
|
99
|
+
- Contract redline and legal review cycle
|
|
100
|
+
- Revenue recognition trigger (IFRS 15 / ASC 606 milestones)
|
|
101
|
+
- Subscription renewal and auto-renewal opt-out
|
|
102
|
+
- Churn risk scoring and save desk workflow
|
|
103
|
+
- Commission calculation and dispute handling
|
|
104
|
+
|
|
105
|
+
**Key metrics:** Quote-to-Close Cycle Time, Win Rate, Contract Renewal Rate, Churn Rate, ACV/TCV.
|
|
106
|
+
|
|
107
|
+
---
|
|
108
|
+
|
|
109
|
+
## Customer Service — Case Management
|
|
110
|
+
|
|
111
|
+
Common gaps to probe:
|
|
112
|
+
- Channel intake — email, phone, chat, social, portal — and unified queue
|
|
113
|
+
- Auto-acknowledgement and SLA clock start
|
|
114
|
+
- Knowledge base deflection rate
|
|
115
|
+
- Escalation matrix — Tier 1 → 2 → 3 → Management
|
|
116
|
+
- Customer satisfaction (CSAT) survey trigger
|
|
117
|
+
- Refund / compensation approval thresholds
|
|
118
|
+
- Regulatory complaint handling (FCA, GDPR, etc.)
|
|
119
|
+
|
|
120
|
+
**Key metrics:** First Contact Resolution (FCR), AHT, CSAT/NPS, Escalation Rate, SLA Compliance, Backlog Age.
|
|
121
|
+
|
|
122
|
+
---
|
|
123
|
+
|
|
124
|
+
## Legal / Compliance — Contract Lifecycle / Audit / GDPR
|
|
125
|
+
|
|
126
|
+
Common gaps to probe:
|
|
127
|
+
- Contract lifecycle stages — initiation, drafting, negotiation, execution, renewal, expiry
|
|
128
|
+
- Redline turnaround time and version control
|
|
129
|
+
- Signature workflow — wet vs. electronic (DocuSign, Adobe Sign)
|
|
130
|
+
- Contract retention schedule and archival
|
|
131
|
+
- GDPR / Data Subject Request (SAR) intake and turnaround (30-day statutory deadline)
|
|
132
|
+
- Audit evidence collection — what gets logged, where, for how long
|
|
133
|
+
|
|
134
|
+
**Key metrics:** Contract Cycle Time, SAR Completion Rate, Audit Finding Close Rate, Contract Renewal Rate.
|
|
@@ -0,0 +1,297 @@
|
|
|
1
|
+
# Interview Spine
|
|
2
|
+
|
|
3
|
+
Use this file to decide how the conversation moves. The phase guides define
|
|
4
|
+
artifacts; this spine defines the interview behavior that prevents premature
|
|
5
|
+
map and document generation.
|
|
6
|
+
|
|
7
|
+
## Core Loop
|
|
8
|
+
|
|
9
|
+
1. Intake evidence: user text, attachments, recordings, project context, and existing wiki content.
|
|
10
|
+
2. Run the initial Process Knowledge retrieval as soon as the process can be named; an opener that opts out of reference processes sends `"no-reference"` instead (SKILL.md, Ordering).
|
|
11
|
+
3. Build a candidate understanding from evidence plus Process Knowledge.
|
|
12
|
+
4. Classify every gap:
|
|
13
|
+
- `known` — directly supported by user, documents, recordings, or confirmed wiki content; numbers, thresholds, and SLAs are carried verbatim from source, never rounded, softened, or ranged.
|
|
14
|
+
- `safe assumption` — low-risk default; record the assumption and rationale.
|
|
15
|
+
- `needs confirmation` — likely answer exists, but wrong answer would matter.
|
|
16
|
+
- `blocking` — answer changes process shape, route, ownership, integration, exception path, SLA, compliance, or terminal outcome.
|
|
17
|
+
5. Ask only the highest-value blocking or high-rework-risk gap.
|
|
18
|
+
6. Run follow-up retrieval at the phase checkpoints and whenever confirmed context materially changes — never while the latch holds (SKILL.md, The latch).
|
|
19
|
+
7. Re-rank gaps after every answer.
|
|
20
|
+
8. Write and validate the map before its Process Snapshot or Future Process Review. A source-derived AS-IS map is provisional until the Process Snapshot confirms it.
|
|
21
|
+
9. Advance only after explicit confirmation of the business shape.
|
|
22
|
+
|
|
23
|
+
A diagram, file, or task list row existing is not completion. Completion means
|
|
24
|
+
the user has confirmed the relevant business shape.
|
|
25
|
+
|
|
26
|
+
## Question Policy
|
|
27
|
+
|
|
28
|
+
Do not run a fixed questionnaire. Use the question bank as coverage, not
|
|
29
|
+
sequence.
|
|
30
|
+
|
|
31
|
+
Ask when the answer changes:
|
|
32
|
+
- route: BPMN vs Case vs RPA
|
|
33
|
+
- existing vs net-new
|
|
34
|
+
- current or future process shape
|
|
35
|
+
- ownership or stage/activity responsibility
|
|
36
|
+
- system or integration design
|
|
37
|
+
- exception, rework, or escalation path
|
|
38
|
+
- SLA, timing, volume, or backlog framing
|
|
39
|
+
- compliance or control obligations
|
|
40
|
+
- terminal outcome
|
|
41
|
+
- PDD credibility
|
|
42
|
+
|
|
43
|
+
Otherwise default the value, mark it as an assumption, carry it as an open
|
|
44
|
+
item, or leave it editable in the next checkpoint.
|
|
45
|
+
|
|
46
|
+
Best-assumption default: when sources (documents, recordings, wiki) answer or
|
|
47
|
+
clearly imply a value, capture it with provenance instead of asking — stated
|
|
48
|
+
evidence is `known`; implied evidence is a `safe assumption` disclosed in the
|
|
49
|
+
next checkpoint's assumption ledger ("What I assumed from your documents").
|
|
50
|
+
A question is spent only on `blocking` gaps, and blocking gaps are batched
|
|
51
|
+
into the checkpoint turn rather than dribbled one per turn. Checkpoints are
|
|
52
|
+
confirm-or-correct surfaces: present what you decided and ask what should
|
|
53
|
+
change.
|
|
54
|
+
|
|
55
|
+
Anchor test: every question names what it comes from — a step, rule, or
|
|
56
|
+
sentence in the sources, or something the user said ("Case 1 says to contact
|
|
57
|
+
the stakeholder — if they never reply, how long does the cart wait?"). A
|
|
58
|
+
question you cannot anchor comes from a generic PDD checklist, not from this
|
|
59
|
+
process: carry it as an open item instead. The interview is an anchor too: in a
|
|
60
|
+
No Docs interview, a layer the user has not covered yet (decisions,
|
|
61
|
+
exceptions, systems/data, volume/SLA, pain points), or a FACTS row the task
|
|
62
|
+
list still shows as missing, is a question in its own right, asked in the
|
|
63
|
+
user's terms. The anchor test filters checklist questions out of a source; it
|
|
64
|
+
never shortens the interview. Where you can, phrase it as your assumption
|
|
65
|
+
plus what it changes, so the user can answer with a yes.
|
|
66
|
+
|
|
67
|
+
Plain-language rule: every question to the user is one or two conversational
|
|
68
|
+
sentences — no markdown tables, bullet lists, or long chunks inside a
|
|
69
|
+
question. Every options question carries a final "Take your best assumption"
|
|
70
|
+
option (except the screenshot and future-state questions, whose options are
|
|
71
|
+
fixed) — the user's fast-forward: decide per the best-assumption default,
|
|
72
|
+
disclose in the ledger, move on. Example of the main-path ask, correctly phrased:
|
|
73
|
+
|
|
74
|
+
> "Could you walk me through what happens, from the moment an invoice
|
|
75
|
+
> arrives until it's paid — just the way you'd explain it to a new teammate?
|
|
76
|
+
> If it's easier to show than tell, record a quick walkthrough or drop in any
|
|
77
|
+
> document you have."
|
|
78
|
+
|
|
79
|
+
(with the Record + Attach widget on the same ask).
|
|
80
|
+
|
|
81
|
+
When the user struggles to describe a step or screen flow (vague answer,
|
|
82
|
+
repeated corrections, "hard to explain"), send a media AskUser with
|
|
83
|
+
`recordable: true`: ask them to record a short demonstration instead of
|
|
84
|
+
describing. Process the result per recording-processing.md.
|
|
85
|
+
|
|
86
|
+
Before generating the PDD, treat these as PDD-critical even when they do not
|
|
87
|
+
change the map: scope boundaries, RACI, KPI targets / acceptance criteria,
|
|
88
|
+
decision-driving data fields, privacy class, HITL/action fields and available
|
|
89
|
+
actions, exception data state transitions, and compliance evidence. Ask one
|
|
90
|
+
targeted question only when the missing item would make the process document
|
|
91
|
+
misleading or unusable; otherwise record it as an explicit open item with its
|
|
92
|
+
impact.
|
|
93
|
+
|
|
94
|
+
## Prepopulated Answer Pattern
|
|
95
|
+
|
|
96
|
+
After each Process Knowledge retrieval, avoid blank questions when a useful baseline
|
|
97
|
+
exists. Present the likely answer and ask the user to confirm, modify, or
|
|
98
|
+
replace it.
|
|
99
|
+
|
|
100
|
+
Use this pattern:
|
|
101
|
+
|
|
102
|
+
```
|
|
103
|
+
Here is the likely baseline I see:
|
|
104
|
+
- [candidate answer 1]
|
|
105
|
+
- [candidate answer 2]
|
|
106
|
+
- [candidate answer 3]
|
|
107
|
+
|
|
108
|
+
What should change?
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
Options:
|
|
112
|
+
- Looks right
|
|
113
|
+
- Add
|
|
114
|
+
- Remove
|
|
115
|
+
- Modify
|
|
116
|
+
- Replace entirely
|
|
117
|
+
|
|
118
|
+
Use free-text follow-up only after the user selects a change path. Treat
|
|
119
|
+
Process Knowledge as a suggestion, never as truth.
|
|
120
|
+
|
|
121
|
+
## Scenario Modes
|
|
122
|
+
|
|
123
|
+
### Intake Docs or Recordings
|
|
124
|
+
|
|
125
|
+
Read the source material before asking follow-up questions. The extraction
|
|
126
|
+
checkpoint is the phase's single snapshot (AS-IS: the Process Snapshot in
|
|
127
|
+
as-is-capture.md), covering:
|
|
128
|
+
- process purpose
|
|
129
|
+
- trigger and outcome
|
|
130
|
+
- roles and owners
|
|
131
|
+
- systems and source of truth
|
|
132
|
+
- main path or lifecycle
|
|
133
|
+
- decisions and business rules
|
|
134
|
+
- exceptions, rework, and escalations
|
|
135
|
+
- pain points
|
|
136
|
+
- metrics, SLA, volume, or backlog
|
|
137
|
+
- confidence, conflicts, and missing shape-changing facts
|
|
138
|
+
|
|
139
|
+
Fill every dimension best-assumption from the sources first; the checkpoint
|
|
140
|
+
carries the assumption ledger. Enumerate at the source's own granularity —
|
|
141
|
+
do not merge distinct source steps into one generic step to shorten the
|
|
142
|
+
list; collapsing detail here is a coverage defect, not efficiency. Find the
|
|
143
|
+
gaps by walking the source step by step, not by category: the questions worth
|
|
144
|
+
asking sit on its seams — a check with no "otherwise", a wait with no limit, a
|
|
145
|
+
correction loop with no exit, an item that comes back without saying which
|
|
146
|
+
checks run again, a handoff with no channel or resume point, two statements
|
|
147
|
+
that read two ways, a decision value with no stated source. A seam the source
|
|
148
|
+
already closes is not a question. Ask only the blocking or conflicting gaps, in
|
|
149
|
+
one batch alongside the checkpoint. For AS-IS, derive, validate, and show the
|
|
150
|
+
source-derived map as provisional with the Process Snapshot; that snapshot is
|
|
151
|
+
the confirmation. Do not advance from the extracted shape until the user
|
|
152
|
+
confirms it.
|
|
153
|
+
|
|
154
|
+
### No Docs
|
|
155
|
+
|
|
156
|
+
Interview in layers:
|
|
157
|
+
trigger -> outcome -> main path -> decisions -> exceptions -> systems/data ->
|
|
158
|
+
volume/SLA -> pain points.
|
|
159
|
+
|
|
160
|
+
Reflect the shape back every few turns. Do not ask a bare list of unrelated
|
|
161
|
+
questions.
|
|
162
|
+
|
|
163
|
+
### Existing RPA
|
|
164
|
+
|
|
165
|
+
Use the confirmed current process as the baseline. Propose automation units
|
|
166
|
+
from current steps and pain points. Confirm the unit list before mode
|
|
167
|
+
selection.
|
|
168
|
+
|
|
169
|
+
### Net-New RPA
|
|
170
|
+
|
|
171
|
+
Do not create current-state pages. Interview the future automation shape:
|
|
172
|
+
task boundary, trigger, applications/screens, inputs, outputs, rules,
|
|
173
|
+
exceptions, access constraints, volume/frequency, and SLA or time-saved target.
|
|
174
|
+
Confirm the unit list before mode selection.
|
|
175
|
+
|
|
176
|
+
### Existing BPMN
|
|
177
|
+
|
|
178
|
+
Use the confirmed current process as the baseline. Convert pain points,
|
|
179
|
+
handoff gaps, unclear decisions, waits, and informal exception paths into
|
|
180
|
+
proposed target changes; present them inside the Future Process Review as
|
|
181
|
+
"Proposed changes from today's process" — one confirmation covers changes
|
|
182
|
+
and map. If Case is also a plausible fit, the routing question offers both.
|
|
183
|
+
|
|
184
|
+
### Net-New BPMN
|
|
185
|
+
|
|
186
|
+
Do not create current-state pages. Interview the future process model:
|
|
187
|
+
participants/lanes, start and end events, activities/subprocesses, gateways,
|
|
188
|
+
message/timer waits, data objects, systems, exception paths, SLA, and terminal
|
|
189
|
+
outcomes. Confirm participants, handoffs, gateways, waits, and exception routes
|
|
190
|
+
before writing the future map. If the process sounds like a managed lifecycle
|
|
191
|
+
object, offer Case as an alternative and let the user choose.
|
|
192
|
+
|
|
193
|
+
### Existing Case
|
|
194
|
+
|
|
195
|
+
Use the confirmed current process as the baseline. Convert pain points and
|
|
196
|
+
handoff gaps into proposed target changes; present them inside the Future
|
|
197
|
+
Process Review as "Proposed changes from today's process" — one
|
|
198
|
+
confirmation covers changes and map.
|
|
199
|
+
|
|
200
|
+
### Net-New Case
|
|
201
|
+
|
|
202
|
+
Do not create current-state pages. Interview the case object, lifecycle,
|
|
203
|
+
stages, stage work, owners, decisions, exception stages, evidence, systems,
|
|
204
|
+
SLA, and terminal outcomes. Confirm stages and routes before writing the
|
|
205
|
+
future map.
|
|
206
|
+
|
|
207
|
+
## Question Banks — tiered by blocking power
|
|
208
|
+
|
|
209
|
+
A question fires only when (a) sources + Process Knowledge + prior phases
|
|
210
|
+
cannot answer it AND (b) the answer changes the process shape or PDD
|
|
211
|
+
credibility. The tiers below are coverage, never a script; phrase everything
|
|
212
|
+
per the plain-language rule.
|
|
213
|
+
|
|
214
|
+
### AS-IS — Tier 1: Frame (usually answered by the opener or sources)
|
|
215
|
+
|
|
216
|
+
- What process are we documenting, and what does "done" look like for one item?
|
|
217
|
+
- Is this how it works today, or something new you want to design?
|
|
218
|
+
- What kicks it off?
|
|
219
|
+
- Task or process? When the opener looks like a single task, run the Decision 1 double-check immediately (see Routing below).
|
|
220
|
+
|
|
221
|
+
### AS-IS — Tier 2: Shape (blocks the map)
|
|
222
|
+
|
|
223
|
+
- Walk me through the main path, start to finish (with the recording/attach offer — see the phrased example above).
|
|
224
|
+
- Who does each step? Which systems and screens does it touch, and what does it take in / hand off? (only for steps the sources leave silent)
|
|
225
|
+
- Where does the flow branch, and what decides which way it goes?
|
|
226
|
+
- What goes wrong, and what happens then? Where does it rejoin — back into the main path, or does it end the process? (ask this one almost always — sources document the happy path; exceptions, rework, and escalations are the systematically missing dimension)
|
|
227
|
+
|
|
228
|
+
### AS-IS — Tier 3: Credibility (blocks the PDD, not the map — estimates accepted and labeled)
|
|
229
|
+
|
|
230
|
+
- How many come through per day or week? Any peak periods or backlog?
|
|
231
|
+
- How long does one take end to end? Any deadline or service commitment?
|
|
232
|
+
- Any compliance or audit obligations on this process, and at what step are they actually checked or enforced?
|
|
233
|
+
- What hurts most about how it works today?
|
|
234
|
+
|
|
235
|
+
### Routing — two decisions
|
|
236
|
+
|
|
237
|
+
Decision 1 (opener): task vs process. When the opener looks like a discrete
|
|
238
|
+
task, double-check immediately with one plain question ("This looks like a
|
|
239
|
+
single task to automate rather than a full business process — should I treat
|
|
240
|
+
it that way?"; options: Task automation (Recommended) / Full business process /
|
|
241
|
+
Take your best assumption). A confirmed task locks the RPA route — Decision 2
|
|
242
|
+
never fires. A process proceeds silently.
|
|
243
|
+
|
|
244
|
+
AS-IS capture format (Phase 1, before drawing): today's process can be
|
|
245
|
+
captured as a case map, a BPMN model, or a simple flow map. The inputs decide
|
|
246
|
+
when they can (supplied BPMN → verbatim; confirmed task → simple flow map);
|
|
247
|
+
otherwise one explicit question in the pre-drawing batch, recommendation
|
|
248
|
+
first, with "Take your best assumption". The format seeds Decision 2's
|
|
249
|
+
recommendation but never binds it.
|
|
250
|
+
|
|
251
|
+
Decision 2 (TO-BE boundary, processes only): Case vs BPMN, named plainly, with
|
|
252
|
+
the recommendation first and a one-line business explanation each ("Case
|
|
253
|
+
management — track each request through stages, owners, and deadlines" /
|
|
254
|
+
"BPMN — a cross-department process model with events, decisions, and
|
|
255
|
+
handoffs" / "Take your best assumption"). Batch it with the intent questions
|
|
256
|
+
below in one AskUser. Skip when the user already explicitly named the target.
|
|
257
|
+
|
|
258
|
+
### TO-BE — universal intent (all routes)
|
|
259
|
+
|
|
260
|
+
- What should change, and what does success look like?
|
|
261
|
+
- What must NOT change? (systems that stay, teams, regulatory constraints)
|
|
262
|
+
- Have any tooling decisions already been made?
|
|
263
|
+
|
|
264
|
+
### TO-BE — Task automation (RPA)
|
|
265
|
+
|
|
266
|
+
- For each unit: fully automated, assisted, agent, human review, or manual? (the explicit batched mode ask — one AskUser, one single-select question per unit)
|
|
267
|
+
- Where must a person stay involved, and what exactly do they see and decide?
|
|
268
|
+
- What should happen when a step fails mid-run?
|
|
269
|
+
- What starts the future process — a schedule, an event, or a queue?
|
|
270
|
+
|
|
271
|
+
### TO-BE — Case management
|
|
272
|
+
|
|
273
|
+
- Stages: presented confirm-or-correct from the current process, never as a blank question.
|
|
274
|
+
- Who owns each stage, and what must be true before an item leaves it?
|
|
275
|
+
- Which stage work should be automated, and which stays with people?
|
|
276
|
+
- What starts a case — someone creating it, a schedule, or something happening in another system?
|
|
277
|
+
- Can any of these stages be skipped and the case still count as done?
|
|
278
|
+
- When the exception work happens, does everything else pause — and afterwards, does the case pick up where it left off?
|
|
279
|
+
- Within a stage, what happens in order, and what can run side by side?
|
|
280
|
+
- What are all the ways a case can end?
|
|
281
|
+
- Which deadlines matter per stage — and when one is at risk, should someone just be told, or should the case change course?
|
|
282
|
+
- What must be kept as evidence?
|
|
283
|
+
- When each person opens the case, what do they need to see and do?
|
|
284
|
+
|
|
285
|
+
### TO-BE — Process orchestration (BPMN)
|
|
286
|
+
|
|
287
|
+
- Which departments, roles, or systems own parts of the process?
|
|
288
|
+
- Where does work wait — on people, on timers, on outside responses?
|
|
289
|
+
- Which decisions split the flow, and what are the possible outcomes?
|
|
290
|
+
- What runs in parallel?
|
|
291
|
+
- What are all the ways the process can end?
|
|
292
|
+
|
|
293
|
+
### PDD readiness (verify, do not re-interview)
|
|
294
|
+
|
|
295
|
+
- The route, current model, and future model were confirmed at their snapshots — verify, never re-ask.
|
|
296
|
+
- Client name, process name, author, version: best-assume from wiki and sources; ask one plain question only for an unknown client name.
|
|
297
|
+
- Everything else missing becomes an open item in the document with its impact.
|