@uipath/skills 1.196.0 → 1.197.0

package/skills/uipath-planner/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: uipath-planner
 description: "UiPath solution planner & designer. Always invoke for `pdd.md` / `sdd.md` files. Authors a Solution Design Document (SDD) from a Process Design Document (PDD), then derives the multi-skill, multi-project task list and emits live TaskCreate calls. Detects project type (.cs, .xaml, .flow, .bpmn, .py). For `uip solution` init/pack/publish/deploy/activate & `.uipx`→uipath-solution. For non-solution Orchestrator/IS/auth/traces→uipath-platform. For .xaml/.cs→uipath-rpa. For .flow→uipath-maestro-flow. For .bpmn→uipath-maestro-bpmn. For agent.json/.py→uipath-agents. For caseplan.json→uipath-maestro-case."
-when_to_use: "User provides a PDD/SDD, says 'generate SDD'/'analyze this PDD'/design/architect/'turn this PDD into' a UiPath solution (selects product scope), OR makes a non-trivial request spanning SEPARATE buildable projects (a Flow orchestrating standalone RPA processes or agents that must themselves be built, 'build a solution from scratch'). Load BEFORE authoring an SDD or deriving tasks. Skip for SINGLE-project requests — even a Flow/Agent/RPA project with inline HITL/script/connector nodes in its own solution — invoke that specialist directly. Flow calling only existing/deployed processes→uipath-maestro-flow."
+when_to_use: "User provides a PDD/SDD, says 'generate SDD'/'analyze this PDD'/design/architect/'turn this PDD into' a UiPath solution (selects product scope), OR makes a non-trivial request spanning SEPARATE buildable projects (a Flow orchestrating standalone RPA processes or agents that must themselves be built, 'build a solution from scratch'). A PDD or SDD ALWAYS routes here (Phase D) — author its SDD even when it describes ONE RPA process; never hand a raw PDD to a specialist. Load BEFORE authoring an SDD or deriving tasks. Skip ONLY when there is no PDD/SDD and the request targets one project — even a Flow/Agent/RPA project 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, AskUserQuestion, EnterPlanMode, ExitPlanMode, TaskCreate, TaskUpdate, TaskList
 ---
 
@@ -16,7 +16,7 @@ Never execute the work. Outputs are SDD markdown, plan/tasks markdown, and live
 
 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, then fall through into Lane A. See [sdd-generation-guide.md](references/sdd-generation-guide.md).
+- **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](references/sdd-generation-guide.md).
 - **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](references/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](references/non-pdd-lane-guide.md).
 
@@ -34,15 +34,15 @@ The skill has three paths, decided by the **Entry Guard**:
 
 1. **Plan & design only — never author automation code.** Outputs: SDD markdown (Phase D), plan/tasks markdown (Lanes A/B), and live `TaskCreate` calls. NEVER write XAML, C#, Python, JSON, or project/scaffold files. Implementation always routes to a specialist. (SDD/plan authoring is the *only* file authoring this skill does.)
 2. **Run the Entry Guard first.** Inspect the input and route to Phase D / Lane A / Lane B before anything else.
-3. **Select scope before designing architecture (Phase D).** Single product (RPA Process/Library/Test Auto, Maestro Flow, Case, Agents, Coded Apps, API Workflows) vs multi-project Solution determines the template(s) and project structure. Use the [Product Selection Guide](references/product-selection-guide.md): Level 1 → 1.5 (RPA sub-type) → 1.75 (Solution composition) → 2.5 (project decomposition).
+3. **Select scope before designing architecture (Phase D) — and gate every product by platform constraints.** Single product (RPA Process/Library/Test Auto, Maestro Flow, Case, Agents, Coded Apps, API Workflows) vs multi-project Solution determines the template(s) and project structure. Use the [Product Selection Guide](references/product-selection-guide.md): Constraint Gate → Level 1 → 1.5 (RPA sub-type) → 1.75 (Solution composition) → 2.5 (project decomposition). The delivery model (Cloud / Automation Suite / standalone — asked at Phase D entry) blocks unavailable products via [platform-availability-guide.md](references/platform-availability-guide.md); user-excluded products are never re-offered.
 4. **The SDD is architecture only — no task lists.** Phase D produces the SDD (Project Structure, Data Definitions, Testing Strategy, …). Task derivation is Lane A's job. Never put Task 1 / Task N templates or *implementation* `TaskCreate` calls in the SDD. End the SDD with a `## Next Steps` section. (Progress-tracking `TaskCreate` calls are a separate, allowed use.)
-5. **Write the `## Planner Handoff` header AND the `<!-- planner-handoff:v1 -->` marker into every SDD.** Load-bearing detection contract — the Entry Guard detects either signal (redundant on purpose). `Generated by: uipath-planner`. Fields: Execution autonomy, SDD scope, Project list section, Tasks file, Generated by, Generation date.
+5. **Write the `## Planner Handoff` header AND the `<!-- planner-handoff:v1 -->` marker into every SDD.** Load-bearing detection contract — the Entry Guard detects either signal (redundant on purpose). `Generated by: uipath-planner`. Fields: Execution autonomy, Delivery model, SDD scope, Project list section, Tasks file, Generated by, Generation date.
 6. **Honour the template section structure as a hard superset contract.** Write single-product scope to `<PROCESS_NAME_KEBAB>-sdd.md`; write Solution scope to a `<SOLUTION_NAME_KEBAB>-solution-sdd.md` overview plus one `<PROJECT_NAME_KEBAB>-sdd.md` per project. If the user specifies an output path for the SDD, use it instead of these defaults. After writing, diff the generated H2/H3 headings against the template TOC — the generated set MUST be a superset. A missing template-required H2 is an SDD defect, not an `[SME REVIEW]` item — regenerate it.
 7. **Testing is mandatory and thorough — never offer "happy path only".** Phase D writes a full §17 Testing Strategy (happy path, edge cases, error scenarios, e2e for Master Projects). The plan adds a mandatory Testing task **per generation skill**, routing to that specialist's testing references — never describing the procedure inline. Implementation specialists may scope down at execution time; the SDD and plan do not.
 8. **Route — do not redescribe.** The plan says WHICH skill to load and IN WHAT ORDER. It does NOT describe specialist-internal flows (target configuration, OR registration, XAML pipelines, HITL field/outcome schema, auth, testing procedures). For a HITL step, pass business intent only ("manager approves or rejects an expense; can add a reason if rejected") — never a field-level spec; the HITL specialist chooses the schema shape.
 9. **Per-phase prompt budget.** Phase D runs under its own checkpoint model (see [sdd-generation-guide.md](references/sdd-generation-guide.md)) — no hard numeric cap. Lanes A and B each cap at **5 `AskUserQuestion` calls**. Ask **execution autonomy exactly once** (Phase D entry) and write it into the handoff header; Lane A reads it and never re-asks. Scope/UI answers resolved in Phase D flow forward via the SDD.
 10. **Fill gaps with `[DEFAULT]` or `[SME REVIEW]` — never silently invent business rules.** `[DEFAULT]` for industry-standard patterns (retry counts, timeouts); `[SME REVIEW]` for business-knowledge gaps. Resolve `[SME REVIEW]` items with the user before writing. For Agent/Coded App gaps, use `AskUserQuestion` (proceed-with-gap-filling vs different product) — never auto-fallback.
-11. **The terminal artefact of a Solution build is a packed `.uipx`.** The SDD's §18 Next Steps points the user at the `uipath-solution` skill (`uip solution init` → `project add` per project → `resources refresh` → `pack`). A bare project folder is not the deliverable.
+11. **The terminal artefact of a Solution build is a packed `.uipx`.** The SDD's §18 Next Steps points the user at the `uipath-solution` skill (`uip solution init` → `project add` per project → `resources refresh` → `pack`). A bare project folder is not the deliverable. Exception: when the Constraint Gate blocks Solutions for the delivery model — standalone, Automation Suite older than 2.2510, or a user exclusion — rewrite §18 to per-package Orchestrator publish routed via `uipath-platform`.
 12. **Never copy SDD architecture into the plan, and never invent selectors or UI targets.** The plan references SDD section paths in skill prompts; it does not duplicate architecture content. Selectors require application inspection at development time — leave them for the specialist.
 
 ## Entry Guard
@@ -82,9 +82,9 @@ Do not pattern-match on filename or extension alone; those are unreliable. The `
 
 When triggered: input is a PDD, or an explicit design/architect request. Three phases; full detail in [sdd-generation-guide.md](references/sdd-generation-guide.md). All user questions use numbered-choice format.
 
-1. **Phase 1 — PDD Analysis & Scope Selection.** Ask execution mode (Autonomous or Interactive). Read the full PDD, extract structured information, run Level 1 (primary scope) → Level 1.5 (RPA sub-type) → Level 1.75 (Solution composition) → Level 2.5 (project decomposition). Step 2.5 runs an authenticated `uip` library search (CLI auth required). In Interactive mode, present a summary with the recommended scope at the top and alternatives below; in Autonomous mode, proceed.
+1. **Phase 1 — PDD Analysis & Scope Selection.** Ask execution mode (Autonomous or Interactive) and delivery model (Cloud / Automation Suite / standalone) in one batched call — skip the delivery question when the PDD or request states it, or when the `uip login status` preflight resolves it from the session `BaseUrl`. Read the full PDD, extract structured information (including environment & constraint signals), run Constraint Gate → Level 1 (primary scope) → Level 1.5 (RPA sub-type) → Level 1.75 (Solution composition) → Level 2.5 (project decomposition). Step 2.5 runs an authenticated `uip` library search (CLI auth required). In Interactive mode, present a summary with the recommended scope at the top and alternatives below; in Autonomous mode, proceed.
 2. **Phase 2 — Architecture Review.** Load the product-specific template. Generate the architectural core sections. Present for review in Interactive mode.
-3. **Phase 3 — Full SDD Generation.** Generate all remaining sections including the thorough §17 Testing Strategy. Resolve `[SME REVIEW]` items first. Write the `## Planner Handoff` header + marker. Write the SDD to disk. **Fall through into Lane A** to derive tasks.
+3. **Phase 3 — Full SDD Generation.** Generate all remaining sections including the thorough §17 Testing Strategy. Resolve `[SME REVIEW]` items first. Write the `## Planner Handoff` header + marker. Write the SDD to disk — write early and append incrementally so a long turn still leaves a gradeable file. The SDD write is a **turn boundary**: in autonomous mode, end the turn after the SDD summary and continue into Lane A on the next turn (do not stack both phases in one turn).
 
 ## Lane A — PDD-driven (summary)
 
@@ -138,10 +138,13 @@ High-level view of what each specialist owns. **Do not describe internal flows o
 |------|---------|
 | [SDD Generation Guide](references/sdd-generation-guide.md) | Phase orchestrator — Phase 1, 2, 3 step-by-step instructions |
 | [PDD Analysis Guide](references/pdd-analysis-guide.md) | How to extract structured data from PDDs in any format |
-| [Product Selection Guide](references/product-selection-guide.md) | **Level 1** (primary scope), **Level 1.75** (Solution composition), **Level 2.5 Part B** (cross-product project list merge), **Level 3** (capability add-ons), template mapping |
+| [Product Selection Guide](references/product-selection-guide.md) | **Constraint Gate** (delivery model + exclusions filter), **Level 1** (primary scope), **Level 1.75** (Solution composition), **Level 2.5 Part B** (cross-product project list merge), **Level 3** (capability add-ons), template mapping |
+| [Platform Availability Guide](references/platform-availability-guide.md) | Product × delivery-model availability matrix (Cloud / Automation Suite / standalone), alternatives for blocked products, verification rule for uncertain cells. Load whenever delivery model ≠ cloud; on cloud every product is available — lookup optional. |
 | [RPA Product Guide](references/rpa-product-guide.md) | RPA **Level 1.5** (sub-type), **Level 2** (authoring mode), **Level 2.5 Part A** (RPA decomposition), R-07 naming, REFramework. Load when Level 1 = RPA or a Solution includes RPA. |
 | [Package Selection Guide](references/package-selection-guide.md) | NuGet package selection; Integration Service vs NuGet rules; per-product dependency manager. Load when filling §14 Packages or equivalent. |
 | [Tenant Library Search Guide](references/tenant-library-search-guide.md) | Step 2.5 procedure for discovering deployed libraries via `uip or libraries list` + JMESPath filtering — auth preflight, ranking, zero-results branch, manual fallback. |
+| [Attended Re-auth Pattern Guide](references/attended-reauth-pattern-guide.md) | Design contract for portal automations with a human-only login (hardware 2FA token, smart card, biometric): handoff point, state-verified resume, attended robot, routing to `uipath-rpa`. Load when the PDD signals a non-scriptable interactive sign-in. |
+| [ASDD Crosswalk Guide](references/asdd-crosswalk-guide.md) | Generate the client-facing Word SDD/ASDD: warn the user for the template path, match the markdown SDD into its sections, compute missing pieces. Includes the crosswalk for the standard UiPath SDD template. Load at Step 2.5 when the user wants the official document. |
 
 ### SDD templates
 
@@ -154,6 +157,13 @@ High-level view of what each specialist owns. **Do not describe internal flows o
 | [Coded App Template](assets/templates/coded-app-sdd-template.md) | SDD template for Coded Apps (web) |
 | [API Workflow Template](assets/templates/api-workflow-sdd-template.md) | SDD template for API Workflows |
 
+### Scripts (Phase D)
+
+| Script | Purpose |
+|------|---------|
+| `scripts/docx-extract.sh` | .docx PDD → UTF-8 markdown + extracted screenshots (pandoc). Run at Phase D Step 1 when a Word PDD renders garbled — never drive Word via COM. |
+| `scripts/sdd-to-docx.sh` | Generated SDD markdown → styled .docx, optional corporate `--reference-doc`. Run at Phase D Step 2.5 only when the user asks for Word output. |
+
 ### Lanes A & B — Planning
 
 | File | Purpose |
@@ -176,3 +186,4 @@ High-level view of what each specialist owns. **Do not describe internal flows o
 9. **Recommending a skill that contradicts filesystem signals.** `.flow` → `uipath-maestro-flow`, not `uipath-rpa`.
 10. **Inventing selectors from screenshots,** or asking the user what the planner / library / filesystem can already answer. Default first; spend a prompt only on decisions only the user can make.
 11. **Renaming the `## Planner Handoff` heading or stripping the `<!-- planner-handoff:v1 -->` marker.** Either signal alone is sufficient for detection, but both should remain — removing both breaks Lane A detection silently.
+12. **Recommending a product the customer's platform cannot run, or re-offering an excluded one.** Defaulting to cloud-modern picks (Maestro, Coded Apps, Document Understanding) on an Automation Suite engagement is the most expensive design error — every blocked product survives review only to fail at delivery. Run the Constraint Gate; once a user says "we don't want X", X stays blocked for the whole session.

package/skills/uipath-planner/assets/templates/agent-sdd-template.md

@@ -20,6 +20,7 @@
 | Field | Value |
 |---|---|
 | **Execution autonomy** | <autonomous \| interactive> |
+| **Delivery model** | <cloud \| automation-suite <VERSION_IF_KNOWN> \| standalone \| unspecified> |
 | **SDD scope** | <single-product \| solution> |
 | **Project list section** | §9 Project Structure |
 | **Tasks file** | `<AGENT_NAME_KEBAB>-tasks.md` |
@@ -45,6 +46,19 @@ Non-RPA scope: rows collapse to scope + product-specific Level-1.5-equivalent.
 
 ---
 
+<!--
+EMIT THIS BLOCK ALWAYS (both execution modes).
+Durable copy of the Phase 1 Recommended Scope summary — the SDD record of the
+Constraint Gate outcome. See product-selection-guide.md → Summary block for the full format.
+-->
+## Recommended Scope
+
+**Recommendation:** <SINGLE_PRODUCT | SOLUTION(<PRODUCT_1>, ...)>
+**Delivery model:** <cloud | automation-suite <version-if-known> | standalone | unspecified — assumed cloud [SME REVIEW]>
+**Blocked by platform:** <PRODUCT → ALTERNATIVE_APPLIED (matrix | user exclusion), ... | none>
+
+---
+
 <!--
 EMIT THIS BLOCK ONLY when at least one [SME REVIEW] item remains after Step 1.5 resolution.
 Skip entirely when no review items are open.

package/skills/uipath-planner/assets/templates/api-workflow-sdd-template.md

@@ -20,6 +20,7 @@
 | Field | Value |
 |---|---|
 | **Execution autonomy** | <autonomous \| interactive> |
+| **Delivery model** | <cloud \| automation-suite <VERSION_IF_KNOWN> \| standalone \| unspecified> |
 | **SDD scope** | <single-product \| solution> |
 | **Project list section** | §10 Project Structure + §5 Connectors |
 | **Tasks file** | `<API_WORKFLOW_NAME_KEBAB>-tasks.md` |
@@ -45,6 +46,19 @@ Non-RPA scope: rows collapse to scope + product-specific Level-1.5-equivalent.
 
 ---
 
+<!--
+EMIT THIS BLOCK ALWAYS (both execution modes).
+Durable copy of the Phase 1 Recommended Scope summary — the SDD record of the
+Constraint Gate outcome. See product-selection-guide.md → Summary block for the full format.
+-->
+## Recommended Scope
+
+**Recommendation:** <SINGLE_PRODUCT | SOLUTION(<PRODUCT_1>, ...)>
+**Delivery model:** <cloud | automation-suite <version-if-known> | standalone | unspecified — assumed cloud [SME REVIEW]>
+**Blocked by platform:** <PRODUCT → ALTERNATIVE_APPLIED (matrix | user exclusion), ... | none>
+
+---
+
 <!--
 EMIT THIS BLOCK ONLY when at least one [SME REVIEW] item remains after Step 1.5 resolution.
 Skip entirely when no review items are open.

package/skills/uipath-planner/assets/templates/case-sdd-template.md

@@ -20,6 +20,7 @@
 | Field | Value |
 |---|---|
 | **Execution autonomy** | <autonomous \| interactive> |
+| **Delivery model** | <cloud \| automation-suite <VERSION_IF_KNOWN> \| standalone \| unspecified> |
 | **SDD scope** | <single-product \| solution> |
 | **Project list section** | §15 Project Structure + §14 Integrated Components |
 | **Tasks file** | `<CASE_NAME_KEBAB>-tasks.md` |
@@ -45,6 +46,19 @@ Non-RPA scope: rows collapse to scope + product-specific Level-1.5-equivalent.
 
 ---
 
+<!--
+EMIT THIS BLOCK ALWAYS (both execution modes).
+Durable copy of the Phase 1 Recommended Scope summary — the SDD record of the
+Constraint Gate outcome. See product-selection-guide.md → Summary block for the full format.
+-->
+## Recommended Scope
+
+**Recommendation:** <SINGLE_PRODUCT | SOLUTION(<PRODUCT_1>, ...)>
+**Delivery model:** <cloud | automation-suite <version-if-known> | standalone | unspecified — assumed cloud [SME REVIEW]>
+**Blocked by platform:** <PRODUCT → ALTERNATIVE_APPLIED (matrix | user exclusion), ... | none>
+
+---
+
 <!--
 EMIT THIS BLOCK ONLY when at least one [SME REVIEW] item remains after Step 1.5 resolution.
 Skip entirely when no review items are open.

package/skills/uipath-planner/assets/templates/coded-app-sdd-template.md

@@ -20,6 +20,7 @@
 | Field | Value |
 |---|---|
 | **Execution autonomy** | <autonomous \| interactive> |
+| **Delivery model** | <cloud \| automation-suite <VERSION_IF_KNOWN> \| standalone \| unspecified> |
 | **SDD scope** | <single-product \| solution> |
 | **Project list section** | §10 Project Structure + §9 Integrated Components |
 | **Tasks file** | `<APP_NAME_KEBAB>-tasks.md` |
@@ -45,6 +46,19 @@ Non-RPA scope: rows collapse to scope + product-specific Level-1.5-equivalent.
 
 ---
 
+<!--
+EMIT THIS BLOCK ALWAYS (both execution modes).
+Durable copy of the Phase 1 Recommended Scope summary — the SDD record of the
+Constraint Gate outcome. See product-selection-guide.md → Summary block for the full format.
+-->
+## Recommended Scope
+
+**Recommendation:** <SINGLE_PRODUCT | SOLUTION(<PRODUCT_1>, ...)>
+**Delivery model:** <cloud | automation-suite <version-if-known> | standalone | unspecified — assumed cloud [SME REVIEW]>
+**Blocked by platform:** <PRODUCT → ALTERNATIVE_APPLIED (matrix | user exclusion), ... | none>
+
+---
+
 <!--
 EMIT THIS BLOCK ONLY when at least one [SME REVIEW] item remains after Step 1.5 resolution.
 Skip entirely when no review items are open.

package/skills/uipath-planner/assets/templates/flow-sdd-template.md

@@ -20,6 +20,7 @@
 | Field | Value |
 |---|---|
 | **Execution autonomy** | <autonomous \| interactive> |
+| **Delivery model** | <cloud \| automation-suite <VERSION_IF_KNOWN> \| standalone \| unspecified> |
 | **SDD scope** | <single-product \| solution> |
 | **Project list section** | §3 Nodes Inventory + §7 Integrated Components |
 | **Tasks file** | `<FLOW_NAME_KEBAB>-tasks.md` |
@@ -45,6 +46,19 @@ Non-RPA scope: rows collapse to scope + product-specific Level-1.5-equivalent.
 
 ---
 
+<!--
+EMIT THIS BLOCK ALWAYS (both execution modes).
+Durable copy of the Phase 1 Recommended Scope summary — the SDD record of the
+Constraint Gate outcome. See product-selection-guide.md → Summary block for the full format.
+-->
+## Recommended Scope
+
+**Recommendation:** <SINGLE_PRODUCT | SOLUTION(<PRODUCT_1>, ...)>
+**Delivery model:** <cloud | automation-suite <version-if-known> | standalone | unspecified — assumed cloud [SME REVIEW]>
+**Blocked by platform:** <PRODUCT → ALTERNATIVE_APPLIED (matrix | user exclusion), ... | none>
+
+---
+
 <!--
 EMIT THIS BLOCK ONLY when at least one [SME REVIEW] item remains after Step 1.5 resolution.
 Skip entirely when no review items are open.

package/skills/uipath-planner/assets/templates/rpa-sdd-template.md

@@ -21,6 +21,7 @@
 | Field | Value |
 |---|---|
 | **Execution autonomy** | <autonomous \| interactive> |
+| **Delivery model** | <cloud \| automation-suite <VERSION_IF_KNOWN> \| standalone \| unspecified> |
 | **SDD scope** | <single-product \| solution> |
 | **Project list section** | <§11 \| §10 + §11 \| Project Inventory> |
 | **Tasks file** | `<PROCESS_NAME_KEBAB>-tasks.md` |
@@ -36,14 +37,28 @@ See sdd-generation-guide.md Phase 3 Step 2 item 3 for the format spec.
 -->
 ## Decisions Made
 
-> Autonomous mode picked the four architectural decisions below without a user checkpoint. Override by rerunning in Interactive mode or by editing the relevant SDD section.
+> Autonomous mode picked the five architectural decisions below without a user checkpoint. Override by rerunning in Interactive mode or by editing the relevant SDD section.
 
 | # | Decision | Picked | One-sentence reason |
 |---|---|---|---|
-| 1 | **Scope** (Level 1) | <SINGLE_PRODUCT_OR_SOLUTION_COMPOSITION> | <REASON> |
-| 2 | **RPA sub-type** (Level 1.5) | <PROCESS_OR_LIBRARY_OR_TEST_AUTOMATION> | <REASON> |
-| 3 | **Authoring mode** (Level 2) | <XAML_OR_CODED_OR_HYBRID> | <REASON> |
-| 4 | **Framework** | <REFRAMEWORK_OR_SEQUENCE> | <REASON> |
+| 1 | **Platform constraints** (Constraint Gate) | <DELIVERY_MODEL; BLOCKED_PRODUCTS_OR_NONE> | <REASON> |
+| 2 | **Scope** (Level 1) | <SINGLE_PRODUCT_OR_SOLUTION_COMPOSITION> | <REASON> |
+| 3 | **RPA sub-type** (Level 1.5) | <PROCESS_OR_LIBRARY_OR_TEST_AUTOMATION> | <REASON> |
+| 4 | **Authoring mode** (Level 2) | <XAML_OR_CODED_OR_HYBRID> | <REASON> |
+| 5 | **Framework** | <REFRAMEWORK_OR_SEQUENCE> | <REASON> |
+
+---
+
+<!--
+EMIT THIS BLOCK ALWAYS (both execution modes).
+Durable copy of the Phase 1 Recommended Scope summary — the SDD record of the
+Constraint Gate outcome. See product-selection-guide.md → Summary block for the full format.
+-->
+## Recommended Scope
+
+**Recommendation:** <SINGLE_PRODUCT | SOLUTION(<PRODUCT_1>, ...)>
+**Delivery model:** <cloud | automation-suite <version-if-known> | standalone | unspecified — assumed cloud [SME REVIEW]>
+**Blocked by platform:** <PRODUCT → ALTERNATIVE_APPLIED (matrix | user exclusion), ... | none>
 
 ---
 
@@ -281,6 +296,20 @@ public enum <EnumName>
 |---|---|---|---|---|---|---|
 | 1 | <APP_NAME> | <WEB/DESKTOP/API> | <URL_OR_PROTOCOL_OR_INTEGRATION_SERVICE> | <SOURCE/TARGET/UTILITY> | <READ/WRITE/READ-WRITE/TRANSIENT> | <PER_RUN/PER_ITEM> |
 
+### Interactive Authentication / Re-auth Handoff
+
+<!-- Conditional subsection. Emit/omit rule and guidance: references/attended-reauth-pattern-guide.md, references/pdd-analysis-guide.md. -->
+
+| Field | Value |
+|---|---|
+| **Application** | <APP requiring the human login> |
+| **Factor the robot cannot supply** | <HARDWARE_TOKEN / SMART_CARD / BIOMETRIC / OTP_DEVICE> |
+| **Handoff point** | <process step where the robot pauses for the human> |
+| **Human action** | <what the person does — e.g., insert token, complete portal login> |
+| **Resume condition (state anchor)** | <observable post-login state the robot verifies before continuing — e.g., authenticated URL reached, dashboard element present> |
+| **No-completion behavior** | [DEFAULT] <e.g., wait 5 min, then abort with notification> |
+| **Design shape** | <A: login-before-handoff \| B: mid-run pause + state-aware resume> |
+
 ---
 
 ## 10. Master Project Architecture
@@ -528,6 +557,7 @@ List every prerequisite required on the robot machine before first run:
 - <e.g., Chrome browser + UiPath Chrome Extension>
 - <e.g., Network access to SharePoint / SAP endpoints>
 - <e.g., Certificate trust for internal CAs>
+- <e.g., Human operator present at the machine for an interactive token login>
 
 ### Scalability & Concurrency
 
@@ -593,6 +623,11 @@ Implementation tasks **do not live in this SDD** — they live in the planner's
 
 ### Terminal artefact — a packed `.uipx` solution
 
+<!-- CONSTRAINT GATE: if the platform-availability-guide blocks Solutions for this SDD's
+     Delivery model (standalone, AS older than 2.2510, or user exclusion), REWRITE this
+     subsection: per-package Orchestrator publish, deploy tasks route to uipath-platform
+     instead of uipath-solution. -->
+
 The build is not finished when the project folder compiles. **The terminal artefact of an SDD-driven build is a packed `.uipx` solution**, not a bare project folder. After the implementation specialist (`uipath-rpa`, `uipath-agents`, etc.) reports its tasks complete, load the **`uipath-solution`** skill and run:
 
 ```bash

package/skills/uipath-planner/references/asdd-crosswalk-guide.md

@@ -0,0 +1,55 @@
+# SDD / ASDD (Client Deliverable) Generation
+
+The markdown SDD this skill writes is the **agent-first** artifact: implementation-oriented, the input to task derivation. The official Word **SDD / ASDD** is the **client-facing** deliverable, in the customer's own section structure. Generate the client document only when the user asks for it (client doc, "official template", `.docx`). The markdown SDD already exists and stays as-is — do not restructure it.
+
+## Procedure
+
+1. **Ask for the template path. Warn the user first:**
+
+   > To produce the official SDD/ASDD I need the path to your Word template — the exact version and section structure you want. Without it I will produce the SDD in this skill's default structure, not the official one.
+
+   Stop and wait for the path. Do not assume or invent the official section layout.
+
+2. **Read the template's section structure:**
+   - `.docx` → run `bash <SKILL_DIR>/scripts/docx-extract.sh "<TEMPLATE>.docx"` and take the heading list (the **Contents** page lists the numbered sections).
+   - `.md` → read the headings directly.
+
+   Match against the standard layout in the crosswalk below. The user's file wins on any naming or ordering difference — follow its sections.
+
+3. **Match** each template section to its markdown-SDD source(s) per the crosswalk.
+
+4. **Compute missing pieces.** For a template section with no direct SDD source, derive it from SDD data when present; when it needs information the SDD does not hold, insert a labelled placeholder and add it to a list the user must fill. Never fabricate.
+
+5. **Assemble** the matched + computed content into the template's section order, then convert:
+
+   ```bash
+   bash <SKILL_DIR>/scripts/sdd-to-docx.sh "<ASSEMBLED>.md" --reference-doc "<TEMPLATE>.docx"
+   ```
+
+## Default crosswalk — standard UiPath SDD/ASDD template
+
+RPA / Master-Project oriented. Left column = the template's sections; fill each from the markdown SDD (RPA template section numbers shown).
+
+| Template section | Fill from the markdown SDD | Notes |
+|---|---|---|
+| Title page — *Project title* | Process / Master Project name (§1, Planner Handoff) | — |
+| **1. PURPOSE** | §1 Process Overview (objective, scope) | Keep the template's standard purpose/focus prose; inject the objective. |
+| **2. AUTOMATED PROCESS DETAILS** — Master Project Name, Robot Type, Orchestrator used?, Scalable, UiPath version | §1 (name) + §16 Deployment Environment (Robot type, Orchestrator, UiPath/Studio version, Scalable) | Direct map. `[SME REVIEW]` carries through where §16 is unfilled. |
+| **3.1 Architectural structure** (diagram) | §10 Master Project Architecture data-flow diagram; §2 Process Map for a single project | Place the Mermaid diagram (render separately if images are needed). |
+| **3.2 Master Project Runtime Details** | Production environment→§16; Prerequisites to run→§16 Runtime Prerequisites; Input Data→§5 Data Definitions; Expected output→§1/§5; How to start→§16 Trigger; Reporting→§16/§8; How is Orchestrator used→§16; Password/compliance→§15 Credentials & Assets + constraints; Stored credentials→§15; List of queue names→§12 Queue Architecture; Schedule→§16; Resolutions→§16 | Assemble one table from several SDD sections. |
+| **3.3 Project name N** (per project) — dev environment, prerequisites, repository, configuration method, reused components, new reusable components | §10/§11 per sub-project; prerequisites→§16; configuration method→§15/§11; reused + new reusable components→§14 Packages / §11 (libraries) | One block per project in §10/§11. Dev-environment name and repository are usually `[SME REVIEW]` → placeholder. |
+| **3.4 Project(s) workflows** — Workflow Name, Description (I/O params) | §3 Detailed Process Steps + §11 Project Structure (workflow list) | — |
+| **3.5 Packages** — Package name, Description | §14 Packages | Direct map. |
+| **3.6 Architectural structure** (2nd diagram) | §12 Queue Architecture diagram, or an alternate §10 view | May duplicate 3.1 in the template — emit the queue/running-order view here. |
+| **4.1 Future improvements** | Out of Scope items + open `[SME REVIEW]` items | Compute candidates; else placeholder for the user. |
+| **4.2 Other remarks** | Assumptions / `[DEFAULT]` notes | Placeholder if none. |
+| **5. GLOSSARY** | The template's standard term list | Reuse as-is; append process-specific terms only if the SDD defined any. |
+
+## Section gaps
+
+- **Template section with no SDD source** → compute from SDD data; if it needs engagement info the SDD lacks (dev-environment names, repository paths, commercials, timeline), leave a labelled placeholder for the user.
+- **SDD section with no template home** (e.g. §17 Testing Strategy, §4 Business Rules, §6 Value Mappings when the template omits them) → append under the nearest fit or an appendix; do not silently drop content.
+
+## Non-RPA SDDs
+
+The standard template is RPA / Master-Project oriented. For a Flow / Case / Agent / Coded App / API Workflow SDD, map that SDD's TOC onto the user's template sections the same way: name and runtime details into 1–2, architecture/diagram into 3.1/3.6, the buildable units into 3.3–3.5, and fold product-specific sections into the nearest runtime or architecture section.

package/skills/uipath-planner/references/attended-reauth-pattern-guide.md

@@ -0,0 +1,43 @@
+# Attended Re-authentication / Hardware-token Handoff Pattern
+
+Use this when a step needs a login the robot cannot perform — a physical hardware 2FA token, smart card, biometric, or any interactive sign-in that cannot be scripted. Cite this pattern in the SDD and route the build to `uipath-rpa`. This guide is the design contract, not the build.
+
+## When to apply
+
+Apply when the PDD's robot-attendance or signing-modality signals show a human must complete authentication: `hardware token`, `smart card`, `physical 2FA`, `OTP device`, `biometric`, `human present for login`.
+
+Rule out automatable factors first. Do NOT apply this when the second factor is a **soft** token the robot can read (Google/Microsoft/Okta TOTP, SMS/email code) — `uipath-rpa` scripts those, no handoff. Apply only for factors no software can supply.
+
+## Choose the design shape
+
+Pick **A** when the login is the first step; pick **B** when authentication recurs or the session expires mid-run.
+
+- **A — Login-before-handoff.** The human completes the token login, then starts or hands off to the attended robot, which uses the authenticated session. No in-process pause.
+- **B — Mid-run pause + resume.** The robot runs to the auth gate, pauses, prompts the human to complete the token login, then verifies the post-login state before continuing.
+
+## Specify the handoff contract (shape B)
+
+Fill the §9 *Interactive Authentication / Re-auth Handoff* subsection with:
+
+1. **Handoff point** — the step where the robot pauses.
+2. **Human action** — exactly what the person does (insert token, complete portal login).
+3. **Resume condition / state anchor** — the observable post-login state the robot checks before continuing (authenticated URL reached, dashboard element present).
+4. **No-completion behavior** — timeout, then abort with notification (`[DEFAULT]` 5 min).
+5. **Attendance** — Attended; record it in §16 Robot type.
+
+## Rules
+
+1. Verify the authenticated state before resuming. Never resume on a fixed delay.
+2. Make the work after the gate idempotent — a failed handoff aborts and reruns; resume from the last committed item, not duplicates.
+3. State the contract once per process. If it re-authenticates at several gates, reference the one contract.
+4. Never design around reading the hardware token value — it cannot be done. The factor is the human's.
+
+## What goes where
+
+Specify in the SDD: the gate as a §2 process-map node; the handoff contract in §9; Attended in §16; a re-auth scenario in §17 (handoff completes → resumes; handoff times out → aborts cleanly).
+
+Route to `uipath-rpa`: the pause mechanism, the state-anchor check, retry/timeout, session handling. Do not name activities or describe the implementation.
+
+## Product reference
+
+Attended robots run in the user's session with a person present; the supported path is the human completing the interactive / MFA login and handing off to the attended robot. See UiPath docs: [attended automations](https://docs.uipath.com/robot/standalone/2024.10/admin-guide/attended-automations), [interactive sign-in](https://docs.uipath.com/robot/standalone/2023.4/admin-guide/setting-up-interactive-sign-in). A physical token cannot be automated — the handoff is required.

package/skills/uipath-planner/references/multi-skill-patterns-guide.md

@@ -34,6 +34,8 @@ A request is **single-skill** when:
 
 `uipath-rpa` does not deploy. Deploy to Orchestrator for solution-bundled RPA goes through `uipath-solution` (`uip solution pack/publish/deploy`). For raw single-package Orchestrator ops not wrapped in a `.uipx`, defer to `uipath-platform`.
 
+> **Attended re-auth handoff is inside the RPA build step, not a separate skill.** When the SDD carries a §9 *Interactive Authentication / Re-auth Handoff* subsection (human-only login — hardware token, smart card, biometric), the `uipath-rpa` build task implements the pause/handoff/state-verified-resume per [attended-reauth-pattern-guide.md](attended-reauth-pattern-guide.md). Pass the handoff contract as business intent; do not split it into its own task or describe the activities.
+
 ## Pattern 2 — Flow with local resources
 
 **When it applies:** Flow and the components it orchestrates are peer sibling projects under one `.uipx` solution at the current working directory. **Components here means separate buildable projects** (a standalone RPA `.xaml`/`.cs` process, a coded agent, a coded app) — each scaffolded as a distinct project routed to its own specialist. Inline flow nodes are **not** components (see the blockquote above); `uipath-maestro-flow` authors them itself in steps 1/4. Each component is scaffolded as part of this plan (or replaced by a placeholder contract when not built here). The flow runs locally / publishes to Studio Web per the plan's `Solution scope`.
@@ -121,6 +123,8 @@ When deriving tasks from an SDD, the planner picks a pattern based on the SDD's
 | API Workflow (single product) | `uipath-api-workflow` + `uipath-solution` for deploy + testing |
 | Agent with RPA tools in §3 Tools | Pattern 5 |
 
+> **Deploy routing is constraint-gated.** When the plan's delivery model blocks Solutions (`.uipx`) per [platform-availability-guide.md](platform-availability-guide.md) — standalone, Automation Suite older than 2.2510, or a user exclusion — every `uipath-solution` deploy/publish step in the table above becomes per-package Orchestrator publish routed to `uipath-platform`.
+
 Cross-project integration order (general rule): **dependencies before dependents**. Build callable resources (RPA processes, API Workflows, agents-as-tools) before the products that consume them (Flows, Cases, parent agents).
 
 ## Pattern composition for Solutions

package/skills/uipath-planner/references/non-pdd-lane-guide.md

@@ -23,6 +23,8 @@ If the entry guard classified a provided document as "Other context", read it be
 
 The batch contains only the questions that survive the skip rules. Build the `AskUserQuestion` call as one tool invocation with one `questions` array entry per surviving item.
 
+**Delivery-model constraint (no standing question).** When the request carries self-hosted signals ("Automation Suite", "on-prem", "self-hosted", "air-gapped"), apply the [Constraint Gate](product-selection-guide.md#constraint-gate) against [platform-availability-guide.md](platform-availability-guide.md) before recommending any product, and record `Delivery model: <value>` in the plan header. If the signals are present but ambiguous (can't tell Suite from standalone), add the delivery-model question from [sdd-generation-guide.md → Step 0](sdd-generation-guide.md#step-0-determine-execution-mode--delivery-model) to the Step 1 batch. No signals → omit the field; do not ask.
+
 ### Question 1 — Generation approach
 
 > How would you like me to work?

package/skills/uipath-planner/references/pdd-analysis-guide.md

@@ -7,7 +7,7 @@ How to extract structured information from Process Design Documents in any forma
 | Format | How to Read | Notes |
 |---|---|---|
 | PDF | Use the Read tool with `pages` parameter. Read in chunks of up to 20 pages. | Screenshots are visible as images — see "Handling Screenshots" below. |
-| Word (.docx) | Read the file directly. | Tables may render differently — verify structure. |
+| Word (.docx) | Do NOT Read directly — convert first with `scripts/docx-extract.sh` (see sdd-generation-guide.md Step 1), then read the markdown + extracted media. | Complex tables may extract as raw HTML `<table>` blocks — parse them; verify structure. |
 | Markdown | Read the file directly. | Easiest format — structure is already parseable. |
 | Pasted text | Process from the conversation context. | Ask the user to paste section by section if the PDD is large. |
 
@@ -20,6 +20,7 @@ When you encounter screenshots in the PDD:
 3. **Do NOT extract** selectors, XPath, CSS, coordinates, colors, or visual layout details — these are determined at development time, not from static images.
 4. **Reference** the screenshot content in the relevant process step's "Remarks" field if useful.
 5. **DO extract concrete data values** shown in the screenshot — sample IDs, names, dates, expected outputs, error messages. These are oracles for the test strategy, not selectors. See "Extract Canonical Examples" below.
+6. **Unreadable media formats (.emf, .wmf):** the Read tool cannot render these (common in Word-extracted media). Do not guess their content — ask the user for a PNG export of the figure, or mark every extraction that depended on it as `[SME REVIEW]` naming the file.
 
 ## Extract Canonical Examples
 
@@ -199,6 +200,25 @@ Watch for:
 - **Email protocol** — when email is an application, extract the protocol signal: IMAP, Exchange/EWS, O365 Graph API, POP3, SMTP. Look for keywords like "IMAP", "Exchange", "O365", "Graph API", "dedicated mailbox". If not specified, mark as `[SME REVIEW]` — do not default to O365.
 - **FTP/SFTP** — note whether the PDD specifies FTP, SFTP, or cloud storage (S3, Azure Blob). Capture host/path if mentioned.
 
+### Environment & Constraint Signals
+
+**Mandatory scan on every PDD.** These constraints gate product selection (see [Product Selection Guide → Constraint Gate](product-selection-guide.md#constraint-gate)). Missing them produces architectures the customer cannot run — the most expensive SDD defect.
+
+| Signal | What to extract | Keyword signals |
+|---|---|---|
+| **Delivery model** | Automation Cloud vs Automation Suite (self-hosted) vs standalone Orchestrator. Capture the Automation Suite version if stated. | "Automation Suite", "self-hosted", "on-prem", "on-premises", "air-gapped", "sovereign", "data residency", "Automation Cloud", `cloud.uipath.com`, internal base URLs |
+| **Product exclusions** | Products the client rules out, with the stated reason. | "we don't want <product>", "can't use", "not licensed for", "no cloud services", "Maestro is excluded" |
+| **Orchestration constraints** | Preferred coordination style when the process needs long-running orchestration. | "Maestro", "Action Center", "state machine", "queues only", "Orchestrator queues" |
+| **Signing modality** | How documents get signed: embedded e-signature service vs token-based qualified signing in a local reader (download → sign locally → upload). | "e-signature", "DocuSign", "Adobe Sign", "qualified signature", "hardware token", "smart card", "signature verification" |
+| **Document storage** | Where documents live: SharePoint, network share, Orchestrator storage bucket, ECM/DMS. **Never assume SharePoint.** | "SharePoint", "shared drive", "network drive", "file server", "DMS", "document archive" |
+| **Robot attendance** | Attended vs unattended, and the reason when stated (e.g., physical 2FA token requires a human at the machine). | "attended", "unattended", "2FA", "hardware token", "OTP", "human present", "user's machine" |
+
+Destinations:
+
+- Delivery model + product exclusions → Phase 1 Step 0 skip rules and the [Constraint Gate](product-selection-guide.md#constraint-gate).
+- Signing modality, document storage, robot attendance → §9 Application Inventory / §16 Deployment Environment (or product equivalents); `[SME REVIEW]` when the PDD handles documents or signatures but leaves the modality ambiguous.
+- **Human-only login (physical hardware 2FA token, smart card, biometric, non-scriptable interactive sign-in)** → do NOT stop at `[SME REVIEW]`. Emit the §9 *Interactive Authentication / Re-auth Handoff* subsection (RPA template) with the handoff contract, set §16 Robot type = Attended, and route the build to `uipath-rpa` per the [attended re-authentication pattern](attended-reauth-pattern-guide.md). A **soft** second factor the robot can read (Google/MS/Okta TOTP, SMS/email code) is scripted by `uipath-rpa` — no handoff subsection.
+
 ### Development Details
 
 Extract:
@@ -263,3 +283,6 @@ After extraction, verify these items exist. Flag missing ones:
 | Test data / canonical case | Run "Extract Canonical Examples" first. Only mark `[SME REVIEW]` if scanning every screenshot, every inline-quoted string, and every example table genuinely returns zero concrete values. Most PDDs carry at least one example. |
 | Reporting requirements | `[DEFAULT]` — Orchestrator logs only (no dedicated report) |
 | Email protocol (when email is used) | `[SME REVIEW]` — needed for package selection (IMAP vs O365 vs Exchange) |
+| Delivery model | Asked at Phase 1 Step 0 when the PDD doesn't state it — never silently default. Gates product availability. |
+| Document storage location (when the process handles documents) | `[SME REVIEW]` — never default to SharePoint |
+| Signing modality (when signatures are mentioned) | `[SME REVIEW]` — embedded e-signature service vs local token-based signing changes the architecture |

package/skills/uipath-planner/references/pdd-driven-lane-guide.md

@@ -6,18 +6,19 @@ When the planner detects a Solution Design Document (SDD) at entry, it runs Lane
 
 ## Step 1 — Read the SDD's Planner Handoff header
 
-The header appears near the top of every SDD — immediately after `## Document History` in per-project SDDs, or as section 2 (right after Solution Overview) in a solution-overview SDD. Read these 6 fields:
+The header appears near the top of every SDD — immediately after `## Document History` in per-project SDDs, or as section 2 (right after Solution Overview) in a solution-overview SDD. Read these 7 fields:
 
 | Field | What the planner does with it |
 |---|---|
 | **Execution autonomy** | `interactive` → enter plan mode for task review before execution. `autonomous` → emit live tasks directly. |
+| **Delivery model** | `cloud` / `automation-suite <version>` / `standalone` / `unspecified`. Propagated as a platform-constraint line into every specialist task prompt (Step 6). |
 | **SDD scope** | `single-product` → one SDD file owns one task list. `solution` → one solution-overview SDD plus one per-project SDD; tasks span all projects. |
 | **Project list section** | Tells the planner where to find the unified project list (e.g., `§10` for RPA, `§3 + §7` for Flow, `Project Inventory` for solution overview). |
 | **Tasks file** | Where to write `<process>-tasks.md`. Phase D proposes a path; Lane A respects it. |
 | **Generated by** | `uipath-planner`. Used in the summary output to tell the user the SDD's provenance. |
 | **Generation date** | `YYYY-MM-DD`. Shown to the user in the summary. |
 
-**Missing or malformed fields:** default `Execution autonomy` to `interactive` (safer), default `SDD scope` to `single-product`, infer `Project list section` from the template type, default `Tasks file` to `<sdd-basename-without-sdd>-tasks.md`. **Track each defaulted field** in a session-local list — Step 8 surfaces them in the user-facing summary so the human reviewer can correct the SDD before tasks are emitted. Do not silently swallow the defaults.
+**Missing or malformed fields:** default `Execution autonomy` to `interactive` (safer), default `Delivery model` to `unspecified` (no constraint propagated — pre-existing SDDs lack the field), default `SDD scope` to `single-product`, infer `Project list section` from the template type, default `Tasks file` to `<sdd-basename-without-sdd>-tasks.md`. **Track each defaulted field** in a session-local list — Step 8 surfaces them in the user-facing summary so the human reviewer can correct the SDD before tasks are emitted. Do not silently swallow the defaults.
 
 **Autonomy override on resume:** if the user's resume message explicitly requests review or interactive handling, honour the message over the header's `Execution autonomy` value (do not re-ask).
 
@@ -78,6 +79,8 @@ Based on the project list, pick the matching pattern from [multi-skill-patterns-
 | API Workflow | API Workflow build + `uipath-solution` publish + testing |
 | Solution scope | Compose patterns per project, sequenced by cross-product integration order (dependencies before dependents) |
 
+> **Deploy routing is constraint-gated.** Before emitting any deploy task, check the handoff header's `Delivery model` against [platform-availability-guide.md](platform-availability-guide.md). When Solutions (`.uipx`) is blocked for that model — standalone, Automation Suite older than 2.2510, or a user exclusion — replace every `uipath-solution` deploy/publish step in the table above with per-package Orchestrator publish routed to `uipath-platform`. An SDD whose §18 the Constraint Gate rewrote already says this; apply the same rule when entering Lane A with a hand-written SDD whose §18 does not.
+
 ## Step 5 — UI element targeting (only when §9 contains UI applications)
 
 If the SDD's §9 Application Inventory contains web / desktop / Citrix applications AND the plan loads `uipath-rpa` for a workflow that interacts with them, ask the UI batch as a single `AskUserQuestion` call (3 questions, batched):
@@ -124,6 +127,7 @@ Walk the project list. For each project, emit task rows per the matched pattern.
 4. **Anti-hallucination rule appended verbatim** to every Skill prompt.
 5. **Blocked-by edges** capture the dependency order — leaf resources before consumers, build before testing, testing before deploy.
 6. **Mandatory testing task per generation skill.** Inserted between generation tasks and any deploy task.
+7. **Propagate the delivery model.** When `Delivery model` is `automation-suite` or `standalone`, append one constraint line to every Skill prompt: "Deployment target: <value> — do not introduce products or features unavailable there." Skip the line for `cloud` / `unspecified`.
 
 ## Step 7 — Write tasks.md
 

package/skills/uipath-planner/references/plan-and-tasks-format.md

@@ -20,6 +20,7 @@ Both share the same task row schema. The difference is the prelude — `<feature
 **Expression language:** VB.NET (XAML only; N/A for coded / AI Agent / Flow / Application)
 **Approach:** <explore-first / simultaneous>
 **Execution autonomy:** <autonomous / interactive>
+**Delivery model:** <cloud / automation-suite <version> / standalone>  <!-- only when delivery signals were present in the request; omit otherwise -->
 **App type:** <web / desktop / citrix / N/A>
 **App state:** <open-and-ready / user-will-open / skip-discovery / N/A>
 **UI targeting:** <agent-builds-you-review / user-indicates / N/A>
@@ -58,6 +59,7 @@ In `interactive` mode this section is optional — the user is available to reso
 **Source SDD:** `<process>-sdd.md`
 **SDD scope:** <single-product / solution>
 **Execution autonomy:** <autonomous / interactive>
+**Delivery model:** <cloud / automation-suite <version> / standalone / unspecified>
 **Generation date:** <YYYY-MM-DD>
 
 > Tasks below are derived from the SDD. The SDD remains the architectural source of truth.