@uipath/skills 1.201.0-preview.604 → 1.201.0-preview.605

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uipath/skills",
-  "version": "1.201.0-preview.604",
+  "version": "1.201.0-preview.605",
   "description": "UiPath agent skills for Claude Code, Codex, Cursor, Copilot, Gemini and OpenCode — RPA, UI automation, UI testing, coded agents/apps/workflows, and troubleshooting. Distributed as the UiPath Claude Code plugin.",
   "author": {
     "name": "UiPath"

package/skills/uipath-planner/SKILL.md

@@ -42,6 +42,9 @@ The skill has three paths, decided by the **Entry Guard**:
 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 finalizing (they gate the `Status: ready` flip, not the Phase 3 Step 0 skeleton write). For Agent/Coded App gaps, use `AskUserQuestion` (proceed-with-gap-filling vs different product) — never auto-fallback.
+    - **These two tokens are the entire gap vocabulary, and their exact string is load-bearing.** Every downstream consumer — the `Action Required — SME Review Items` block, the gap counts, the `Status: ready` flip, Lane A's assumption carry-over, and any reviewer grepping the file — finds these items by exact match on `[SME REVIEW]` / `[DEFAULT]`.
+    - **Write the marker verbatim, with nothing else inside the brackets.** The explanatory note goes *after* the closing bracket: `| UiPath version | [SME REVIEW] not recorded in the PDD |`. Never fold the note inside (`[SME REVIEW — not recorded]`) and never substitute another word (`[PLACEHOLDER]`, `[TBD]`, `[TODO]`, `<fill in>`, `N/A`, prose like "to be confirmed"). A decorated or renamed marker is invisible to every consumer above — the gap silently disappears.
+    - **When you map or copy content out of another document** (a source SDD into a client template, a PDD into an SDD, one SDD section into another), **carry its markers through byte-for-byte.** Re-wording a marker you did not author destroys a gap someone else recorded. Add new markers for the gaps *you* find; never edit the ones already there.
 11. **The terminal artefact of a Solution build is a packed `.uipx`.** The SDD's `## Next Steps` section 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 Next Steps 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.
 13. **Sole author of Case Management SDDs.** Every case design path — conversational, build handoff from `uipath-maestro-case`, draft finalization, PDD-driven — runs the Case Design Lane ([case-design-lane-guide.md](references/case-design-lane-guide.md)), which owns the conversation, the one confirmation, and the write; the case model and its defaults live in [case-design-layers-guide.md](references/case-design-layers-guide.md) and the render contract in the case SDD template. Design time resolves identities only — never schema discovery, project scaffolding, or create-on-missing; those are build concerns, recorded as gate decisions.

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

@@ -18,7 +18,9 @@ The markdown SDD this skill writes is the **agent-first** artifact: implementati
 
 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.
+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, write the literal marker `[SME REVIEW]` followed by what is needed, and add the item to a list the user must fill. Never fabricate.
+
+   > **Marker discipline (see SKILL.md Critical Rule 10).** `[SME REVIEW]` and `[DEFAULT]` are the only gap markers, written verbatim with nothing else inside the brackets — the note goes after the closing bracket (`[SME REVIEW] repository not recorded in the source SDD`). Do not invent a second vocabulary (`[PLACEHOLDER]`, `[TBD]`, `<fill in>`) and do not decorate the marker (`[SME REVIEW — …]`); both are invisible to the reviewer grepping the client document for open items. **Markers already in the source SDD copy through byte-for-byte** — this crosswalk relocates content, it never re-words a gap the SDD author recorded.
 
 5. **Assemble** the matched + computed content into the template's section order, then convert:
 
@@ -37,17 +39,17 @@ RPA / Master-Project oriented. Left column = the template's sections; fill each
 | **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.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]` in §16 — carry the marker through verbatim. |
 | **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. |
+| **4.1 Future improvements** | Out of Scope items + open `[SME REVIEW]` items | Compute candidates; else one `[SME REVIEW]` line for the user. |
+| **4.2 Other remarks** | Assumptions / `[DEFAULT]` notes | One `[SME REVIEW]` line 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.
+- **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), write `[SME REVIEW]` plus what is needed. Every such section ends up carrying the literal `[SME REVIEW]` string — that is how the reviewer finds them.
 - **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

package/version-manifest.json

@@ -1,5 +1,5 @@
 {
   "schemaVersion": 2,
-  "skillsVersion": "1.201.0-preview.604",
+  "skillsVersion": "1.201.0-preview.605",
   "targetCli": "^1.201.0"
 }