UiPath Case Management Authoring Assistant

Builds UiPath Case Management definitions from sdd.md. Generates tasks.md plan, then writes caseplan.json directly via per-plugin JSON recipes. CLI is reserved for read-only metadata fetches (registry, validate, debug, tasks describe, case spec) and solution boundary operations (uip solution init / project add / upload).

When sdd.md is absent, Phase 0 designs the case by best assumption from the request and documents, sweeps for other paths beyond the primary flow, confirms it in ONE SDD-shaped Case Review that mirrors the full design document in scan-friendly sections (case snapshot, data contract, primary and secondary stages/tasks, activation modes, task classification rationale, other paths, rules/tiers, resources, assumptions, and review flags), then starts the build with a template-complete sdd.md written alongside as a reference artifact. When sdd.draft.md is present and the user asks to finalize it, stay in this skill: read the draft as the settled case design, normalize it to the Case Management SDD template, and do not hand off to uipath-planner. Complex / multi-product cases may still be designed with the same workflow; suggest uipath-planner only when the user explicitly requests planning across products.

Scope: two journeys — greenfield (build a new case from sdd.md, user-provided or Phase 0-generated) and brownfield (targeted edits to an existing caseplan.json — see references/brownfield.md). Editing a case that also lives in Studio Web? Brownfield pulls the current server state first (uip solution download / solution projects resync) so re-publish can't silently clobber server-side changes — see brownfield.md § Pull latest first.

When to Use This Skill

• User provides sdd.md and wants Case Management project built
• User asks to create new case management project but has no sdd.md (Phase 0 interview generates one)
• User asks to create new case management project or definition
• User asks to generate implementation tasks from sdd.md or convert spec to plan
• User asks to edit, modify, or update an existing caseplan.json (add/remove a stage or task, change a condition, swap a trigger) — targeted edits skip planning; see references/brownfield.md
• User asks about case management JSON schema — nodes, transitions, tasks, rules, SLA
• User wants to manage runtime case instances (list, pause, resume, cancel) — see references/case-commands.md

Do not use for: .xaml → uipath-rpa. .flow → uipath-maestro-flow. Standalone agents/APIs/processes outside case context → corresponding UiPath skill.