uipath-maestro-case

name	uipath-maestro-case
description	TRIGGER for authoring UiPath Maestro Case plans as `<Name>.case.ts` with the reference-mode TypeScript builder SDK (`@uipath/flow-sdk/case`), compiling to `caseplan.json`, and running the `uip maestro case` check/compile/validate loop. Covers stages, tasks, rules, bindings, published-resource references, and brownfield decompile/edit/recompile. Flow builder authoring → uipath-maestro-flow; structural-core BPMN → uipath-maestro-bpmn. DO NOT TRIGGER for C#/XAML automation → uipath-rpa.
allowed-tools	Bash, Read, Write, Edit, Glob, Grep, AskUserQuestion

UiPath Case Management — TypeScript Builder SDK

Author a Case plan as TypeScript and compile it to schema V30 caseplan.json. The builder declares stages, tasks, conditions, variables, and triggers; a Case plan has no control-flow edges.

Use this file as a router. Read only the reference named by the capability you need, then let TypeScript and case check provide the detailed contract.

Workflow

1. Keep <Name>.case.ts beside this SKILL.md and the workspace package.json.
2. Import from @uipath/flow-sdk/case and default-export a chain ending in .build().
3. Start from the closest staged examples/*.case.ts and change only the scenario data.
4. Run uip maestro case check <Name>.case.ts --source after each structural change.
5. Compile into the scaffolded Case project, then run uip maestro case validate.
6. Run live debug only when the task requires runtime evidence and provides tenant resources.

Capability router

Surface	Builder/API	Reference	Example
Case, stages, and completion	casePlan, stage, completeWhen	CaseBuilder	examples/ClaimReviewSLA.case.ts
Variables and arguments	var, input, output, jsonSchema	CaseBuilder	examples/IntakeBinding.case.ts
Manual, timer, and event starts	manualTrigger, timerTrigger, eventTrigger	Trigger decisions	examples/NightlyRollup.case.ts
Entry, exit, and data gates	rule, when	Rules	examples/ClaimReviewSLA.case.ts
Published UiPath work	process, agent, rpa, apiWorkflow, caseManagement, flowProcess	TaskBuilder	examples/ClaimReviewSLA.case.ts
Human work	action	Human tasks	examples/NotifyOnApproval.case.ts
Connector work and waits	connector, waitForConnector	Connections

Minimal shape

import { casePlan, rule } from '@uipath/flow-sdk/case';

export default casePlan('loan-approval')
  .name('Loan Approval')
  .identifier('LOAN')
  .stage('Review', s => s
    .required()
    .entryWhen(rule('case-entered'), { displayName: 'Case entered' })
    .exitWhen(rule('required-tasks-completed'), { displayName: 'All done', marksStageComplete: true })
    .task('Check Policy', t => t
      .process('check-policy', { folder: 'Shared' })
      .required()
      .entryWhen(rule('current-stage-entered')))
    .task('Manager Approval', t => t
      .action({ title: 'Approve loan', priority: 'High', recipient: '[e-mail]' })
      .((, { : [] }))))
  .(,  s
    .()
    .((, { :  }), { :  })
    .((), { :  })
    .(,  t.().().(())))
  .((), { :  })
  .();

Validation loop

uip maestro case check <Name>.case.ts --source
uip maestro case compile <Name>.case.ts -o <project>/caseplan.json
uip maestro case validate <project>/caseplan.json --output json

check owns source-level invariants and emits teaching diagnostics. Product validation owns the compiled Case contract. Do not repair emitted JSON by hand; change the TypeScript source and rebuild.

Evidence boundary

Static success proves the source and artifact contracts. It does not prove live resource resolution, human outcomes, timers, skipped-task completion behavior, or business-calendar semantics. Read Case runtime decisions when one of those affects the requested outcome.