uipath-planner

name	uipath-planner
description	UiPath solution planner & designer. Always invoke for PDD / SDD files (`pdd.md`, `*-sdd.md`). Authors a Solution Design Document (SDD) from a Process Design Document (PDD) — or from another process-knowledge source (Confluence page, SOP, BPMN model, meeting transcript) — then derives the multi-skill, multi-project task list from an SDD, emitting live TaskCreate calls. Known-product single-project build, no PDD/SDD→that skill; ambiguous/'what should I build'→here. For `uip solution` lifecycle & `.uipx`→uipath-solution. For non-solution Orchestrator/IS/auth/traces→uipath-platform. For .xaml/.cs→uipath-rpa. For .flow→uipath-maestro-flow. For building/editing .bpmn→uipath-maestro-bpmn (a .bpmn as design input routes here). For agent.json/.py→uipath-agents. Sole case-SDD author. For caseplan.json build→uipath-maestro-case.
when_to_use	User provides a PDD/SDD (or another process-knowledge source or a prompt — the planner asks clarifying questions), says 'generate SDD'/'analyze this PDD'/design/architect a UiPath solution, OR makes a non-trivial request spanning SEPARATE buildable projects (a Flow orchestrating RPA processes that must be built, 'build a solution from scratch'). A PDD or SDD ALWAYS routes here (Phase D) — author its SDD even for ONE RPA process; never hand a raw PDD to a specialist. Load BEFORE authoring an SDD or deriving tasks. Skip ONLY when no PDD/SDD and the request targets one project — even with inline HITL/script/connector nodes — invoke that specialist directly. Flow calling only existing/deployed processes→uipath-maestro-flow.
allowed-tools	Bash, Read, Write, Glob, Grep, WebFetch, AskUserQuestion, EnterPlanMode, ExitPlanMode, TaskCreate, TaskUpdate, TaskList

UiPath Planner — Design & Task Derivation

Two jobs, one entry point:

1. Design — turn a Process Design Document (PDD) into an implementation-ready Solution Design Document (SDD). Select scope (single product or multi-project Solution), write the SDD.
2. Plan — derive the per-skill task list from an SDD (or a non-PDD request), route to specialists, emit live TaskCreate calls.

Never execute the work. Outputs are SDD markdown, plan/tasks markdown, and live tasks — implementation always routes to a specialist.

The skill has three paths, decided by the Entry Guard:

• Phase D — Design. Input is a PDD, or an explicit "design / architect this" request. Author the SDD; the SDD write ends the turn, and Lane A continues on the next turn. See sdd-generation-guide.md. Case Management designs run through Phase D's Case Design Lane (case-design-lane-guide.md) — a conversational design ending in ONE Case Review confirmation.
• Lane A — PDD-driven. Input is an SDD with the ## Planner Handoff marker (written by Phase D, or hand-written). Read it, derive tasks, emit live tasks. Zero to two user prompts. See pdd-driven-lane-guide.md.
• Lane B — Non-PDD. No SDD; a non-PDD multi-project request. Elicit preferences, detect project type, write a plan, emit live tasks. 0–3 prompts (5-call cap). See non-pdd-lane-guide.md.

When to Use This Skill

• User provides a PDD or any process-knowledge source — a PDD, Confluence page, BPMN model, meeting/Zoom transcript, SOP, or requirements doc (as PDF / Word / Markdown / .txt / .bpmn / pasted) — and asks to design or build from it → Phase D
• User asks to design / architect / generate an SDD for a UiPath automation → Phase D
• User provides an SDD path → Lane A
• The request is non-trivial — spans separate buildable projects that each need their own specialist (a Flow orchestrating standalone RPA processes or agents that must themselves be built) → Lane B
• The request is — no single specialist clearly matches, or "what can I build?"