UiPath Task Planner

Your job is to derive task lists, route to specialists, and emit live tasks — never execute the work yourself.

The planner has two lanes:

• Lane A — PDD-driven. Triggered when the input is an SDD with a ## Planner Handoff header. Reads the SDD, derives tasks per the project list, writes <process>-tasks.md, emits live TaskCreate calls. Zero or one user prompt. See pdd-driven-lane-guide.md.
• Lane B — Non-PDD. Triggered when there's no SDD. Elicits preferences via a batched AskUserQuestion, detects project type, multi-skill patterns or filesystem signals, writes <feature>.md, emits live tasks. Typically 0–3 user prompts (5-call hard cap). See non-pdd-lane-guide.md.

The lane is decided by the Entry Guard below.

When to Use This Skill

• The request is non-trivial — spans separate buildable projects that each need their own specialist (e.g. a Flow orchestrating standalone RPA processes or agents), or UI automation with unclear scope
• The request is ambiguous — no single specialist skill clearly matches
• The user asks "what can I build?" or needs help choosing a project type
• The user provides an SDD path — Lane A runs

Skip this planner for single-project tasks — load the specialist directly. A request is single-project (one specialist owns it end-to-end) even when it bundles several things inside one project: a Flow with script nodes plus an inline HITL approval step plus its own solution wrapper is one uipath-maestro-flow task. Inline nodes (HITL QuickForm, script, connector, inline agent) and the solution scaffolding are author sub-steps the specialist performs itself — they are not separate skills to orchestrate. Counting them as distinct skills ("solution + flow + human-in-the-loop") and emitting a plan is the most common mis-trigger. The planner is only for requests spanning separate buildable projects — distinct .uipx projects (a Flow consuming standalone RPA processes, an Agent using published processes as tools).