Skip to content

Commit 4f23464

Browse files
RaduAna-Mariaclaude
andcommitted
Point uipath-maestro-case at the planner's case product guide
Drops the sdd-viewer.html mention and the stale evals file, and updates the case tasks for the moved planner guide. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1 parent 7b9a30c commit 4f23464

12 files changed

Lines changed: 25 additions & 229 deletions

File tree

‎skills/uipath-maestro-case/SKILL.md‎

Lines changed: 7 additions & 7 deletions
Large diffs are not rendered by default.

‎skills/uipath-maestro-case/references/evals/evals.json‎

Lines changed: 0 additions & 204 deletions
This file was deleted.

‎skills/uipath-maestro-case/references/planning.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -75,9 +75,9 @@ Outside the fast path, do not inspect `~/.uip/case-resources/` first to decide w
7575
7676
Accept the `sdd.md` file path from the user, or ask if not provided. When the directory contains multiple `.md` files, use **AskUserQuestion** with the candidates + "Something else" to disambiguate.
7777
78-
If the resolved path has **no `sdd.md`**, the skill hands the design to the `uipath-planner` Case Design Lane in this conversation before this step (SKILL.md Rule 16 + § Design handoff). Phase 1 begins after the Case Review's Build answer, once the lane has written `sdd.md`. The in-memory model that rendered the file drives planning directly (Rule 2 — do not re-read the just-written file); the Case Review is approval context, not a parsing source.
78+
If the resolved path has **no `sdd.md`**, the skill hands the design to the `uipath-planner` case design path in this conversation before this step (SKILL.md Rule 16 + § Design handoff). Phase 1 begins after the Case Review's Build answer, once the case design path has written `sdd.md`. The in-memory model that rendered the file drives planning directly (Rule 2 — do not re-read the just-written file); the Case Review is approval context, not a parsing source.
7979
80-
`sdd.md` is the **sole required input**. It describes stages, tasks, conditions, SLA, component types, persona information, and provides the search keys for registry lookups. The portable name is type-specific: `Resolved Resource` for process/agent/rpa/api-workflow/function/business-rule, the Action App title in `HITL Implementation` for action, and `Child Case` for case-management. The corresponding identity cell (`Resource Identity` or `Action App ID`) says whether an earlier phase resolved it. (The SDD does not describe edges — transitions are stage entry/exit conditions; Rule 21.) The skill does not validate or gap-fill sdd.md — trust it as written. (The delegated design lane may have produced it; once approved, Rule 2 applies regardless of source.)
80+
`sdd.md` is the **sole required input**. It describes stages, tasks, conditions, SLA, component types, persona information, and provides the search keys for registry lookups. The portable name is type-specific: `Resolved Resource` for process/agent/rpa/api-workflow/function/business-rule, the Action App title in `HITL Implementation` for action, and `Child Case` for case-management. The corresponding identity cell (`Resource Identity` or `Action App ID`) says whether an earlier phase resolved it. (The SDD does not describe edges — transitions are stage entry/exit conditions; Rule 21.) The skill does not validate or gap-fill sdd.md — trust it as written. (The planner may have produced it; once approved, Rule 2 applies regardless of source.)
8181
8282
> **Cache-state distinction — mandatory.** Step 1 refreshes discovery state; it does not validate or override sdd.md. Before a successful pull, a missing cache directory or type index is a failed refresh precondition, not evidence that the SDD resource is unavailable. After a successful pull, search by the SDD's concrete portable name; only an empty exact-name match set (or a still-absent type index) is a genuine empty lookup. An `<UNRESOLVED>` identity or folder means name-only discovery, not permission to skip discovery.
8383
@@ -196,7 +196,7 @@ Use the same section-batched write discipline the caseplan uses — one Read per
196196
> | `action` | `selected.name` | `selected.folder` | `selected.identifier` (`identifierField: "id"`) |
197197
> | `case-management` | `selected.name` | `selected.folder` | `selected.identifier` (`identifierField: "entityKey"`) |
198198
>
199-
> A ledger persisted verbatim from the planner lane (SKILL.md Rule 3) carries the raw cache object instead; read it by the index's own fields — for `action`, `selected.deploymentTitle`, `selected.deploymentFolder.fullyQualifiedName`, `selected.id`; for `case-management`, `selected.name`, `selected.folders[0].fullyQualifiedName`, `selected.entityKey`.
199+
> A ledger persisted verbatim from the planner (SKILL.md Rule 3) carries the raw cache object instead; read it by the index's own fields — for `action`, `selected.deploymentTitle`, `selected.deploymentFolder.fullyQualifiedName`, `selected.id`; for `case-management`, `selected.name`, `selected.folders[0].fullyQualifiedName`, `selected.entityKey`.
200200
201201
## Step 5 — Hand off to Phase 2 (auto-proceed)
202202

‎skills/uipath-maestro-case/references/plugins/sla/planning.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -74,7 +74,7 @@ Rules are evaluated in insertion order — first truthy expression wins. The def
7474

7575
## Identity Resolution
7676

77-
When sdd gives an escalation recipient as an email (`User: manager@corp.com`) or group name (`UserGroup: "Order Management Team"`), resolve to a directory UUID via `uip admin` while authoring the escalation rule. Resolved UUIDs land in `recipients-resolved.json`; [`impl-json.md`](impl-json.md) writes them straight into `escalationRule[].action.recipients[].target` — no sentinel needed. Resolution runs **Phase 1 only** — the design lane records email / group name as a string in sdd.md.
77+
When sdd gives an escalation recipient as an email (`User: manager@corp.com`) or group name (`UserGroup: "Order Management Team"`), resolve to a directory UUID via `uip admin` while authoring the escalation rule. Resolved UUIDs land in `recipients-resolved.json`; [`impl-json.md`](impl-json.md) writes them straight into `escalationRule[].action.recipients[].target` — no sentinel needed. Resolution runs **Phase 1 only** — the planner records email / group name as a string in sdd.md.
7878

7979
### Skip — UUID pass-through
8080

‎skills/uipath-maestro-case/references/registry-discovery.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ During sdd.md → task.md interpretation, when you need to determine:
1313
<!--skill-flavor:prerequisite-login:start-->
1414
Run `uip login status --output json`, then
1515
<!--skill-flavor:prerequisite-login:end-->
16-
`uip maestro case registry pull`, before any cache inspection or lookup. This is a Phase 1 hard gate, not a conditional refresh: never inspect the cache first and use its absence to skip the pull. **One exception — same-session fast path (SKILL.md Rule 3):** when the delegated design lane's pull (`uipath-planner`, SKILL.md Rule 16) already succeeded in this session and `sdd.md` was just written from the confirmed in-memory model, reuse that cache instead of re-pulling — and run verify-only against the planner's resolution ledger (SKILL.md Rule 3); any doubt runs the gate in full. Login/pull failure stops Phase 1 before planning artifacts are written. A pull that exits 0 with `Data.Errors` is partial, not failed: read the rows, and route each 5xx `typecache-*` row to [connector-integration.md § Catalog unavailable](connector-integration.md#catalog-unavailable-typecache-5xx); a 401 or 403 row is a login or permission failure that stops Phase 1 like any pull failure. The design lane grounds lazily: it starts the same login → pull chain in the background only when the case first shows tenant-bound work, then runs full identity resolution plus the ambiguity/empty gate at Case Review time — no schema discovery there; schemas stay a Phase 2/3 concern. A successful pull populates the local cache at `~/.uip/case-resources/`. Discovery reads those cache files — through `sdd resolve` first, and directly by hand for what it leaves — **do not** rely on `uip maestro case registry search` as the primary discovery method. See § When a search returns nothing below for the reason.
16+
`uip maestro case registry pull`, before any cache inspection or lookup. This is a Phase 1 hard gate, not a conditional refresh: never inspect the cache first and use its absence to skip the pull. **One exception — same-session fast path (SKILL.md Rule 3):** when the planner's design-time pull (`uipath-planner`, SKILL.md Rule 16) already succeeded in this session and `sdd.md` was just written from the confirmed in-memory model, reuse that cache instead of re-pulling — and run verify-only against the planner's resolution ledger (SKILL.md Rule 3); any doubt runs the gate in full. Login/pull failure stops Phase 1 before planning artifacts are written. A pull that exits 0 with `Data.Errors` is partial, not failed: read the rows, and route each 5xx `typecache-*` row to [connector-integration.md § Catalog unavailable](connector-integration.md#catalog-unavailable-typecache-5xx); a 401 or 403 row is a login or permission failure that stops Phase 1 like any pull failure. The planner resolves identities only — no schema discovery at design time; schemas stay a Phase 2/3 concern. A successful pull populates the local cache at `~/.uip/case-resources/`. Discovery reads those cache files — through `sdd resolve` first, and directly by hand for what it leaves — **do not** rely on `uip maestro case registry search` as the primary discovery method. See § When a search returns nothing below for the reason.
1717

1818
> **Missing file ≠ empty match.** Before searching any `<type>-index.json`, verify it exists on disk. If it does not, run `uip maestro case registry pull` (not `--force` — a normal pull is enough for first-time population). A missing file **before** a pull is a precondition failure, not a 0-result lookup. **After a pull that synced that type — it is in `Data.ResourceTypes[]`, not `Data.Errors[]` — a still-absent index means the tenant has zero resources of that type — which IS the genuine 0-matches case.** A type in `Data.Errors[]` is not pulled and not empty; for `typecache-*` see [connector-integration.md § Catalog unavailable](connector-integration.md#catalog-unavailable-typecache-5xx). For **non-creatable** types (regular RPA process, agentic processes / Process Orchestration, action, case-management, connectors) → proceed to placeholder. For a **creatable** type (`agent`, `api-workflow`, `business-rule`), a zero-resource tenant index is the genuine 0-matches case where inline **Create** applies — but **first resolve any in-solution sibling** (a prior run may have already built it; see the per-type pre-gate checks — [agent/planning.md](plugins/tasks/agent/planning.md#registry-resolution), [api-workflow/planning.md](plugins/tasks/api-workflow/planning.md#registry-resolution), [business-rule/planning.md](plugins/tasks/business-rule/planning.md#registry-resolution) — and § Handle Empty Results below). Only a resource absent from **both** the tenant index **and** the local siblings is genuinely empty → feed it to the [Rule 18 / § MUST-Confirm gate](#must-confirm-before-placeholder-fallback) (Create offered), NOT straight to placeholder.
1919

@@ -64,7 +64,7 @@ Direct cache-file inspection is the authoritative discovery method for this skil
6464
6565
## MUST Confirm Before Placeholder Fallback
6666
67-
> **Design-time gate short-circuit.** When the same-session resolution ledger from the planner's Case Design Lane (SKILL.md Rule 16) carries a `gateDecision` for a resource, the gate below already ran — the USER answered it at the Case Review (`gateDecision` exists only for user-answered items; a defaulted `resolve at build` carries none and gets the full gate below). Execute the decision without re-asking: `pick:<name>` → bind that entry; `resolve-at-build` → placeholder path directly; `create-during-build` → the Create-on-Missing flow below as if the user picked `Create`. Re-ask ONLY when the entry is stale against the current SDD (carryover rules in [planning.md](planning.md)) or the cache no longer contains the picked entry.
67+
> **Design-time gate short-circuit.** When the same-session resolution ledger from the planner's case design path (SKILL.md Rule 16) carries a `gateDecision` for a resource, the gate below already ran — the USER answered it at the Case Review (`gateDecision` exists only for user-answered items; a defaulted `resolve at build` carries none and gets the full gate below). Execute the decision without re-asking: `pick:<name>` → bind that entry; `resolve-at-build` → placeholder path directly; `create-during-build` → the Create-on-Missing flow below as if the user picked `Create`. Re-ask ONLY when the entry is stale against the current SDD (carryover rules in [planning.md](planning.md)) or the cache no longer contains the picked entry.
6868
6969
> **Hard gate.** If the planning-phase lookup batch returns ≥1 empty result (no match across all relevant cache files for any task / trigger / connector), STOP. Run AskUserQuestion before invoking any per-plugin Unresolved Fallback path or writing any placeholder element.
7070

‎tests/tasks/uipath-maestro-case/_shared/case_check.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -209,7 +209,7 @@ def normalize_audit_entry(entry: dict) -> dict:
209209
def registry_audit_entries(payload: object) -> list[dict]:
210210
"""Read every legal registry-audit representation as one list of entries.
211211
212-
Accepts a bare list (hand-written, and the planner lane's verbatim ledger),
212+
Accepts a bare list (hand-written, and the planner's verbatim ledger),
213213
a `resolutions` / `resources` envelope, and `uip maestro case sdd resolve`'s
214214
own `{resolved, unresolved, scope}` object. Entries come back normalized by
215215
`normalize_audit_entry`, so a grader asserts one shape whichever wrote it.

‎tests/tasks/uipath-maestro-case/_shared/rule_types.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@
2121

2222
HERE = Path(__file__).resolve().parent
2323
SNAPSHOT = HERE / "rule_types.json"
24-
GUIDE = HERE.parents[3] / "skills" / "uipath-planner" / "references" / "case" / "case-design-layers-guide.md"
24+
GUIDE = HERE.parents[3] / "skills" / "uipath-planner" / "references" / "design" / "case-product-guide.md"
2525

2626
# The layers guide's § Lifecycle gates row label for each declared scope.
2727
GUIDE_ROWS = {

‎tests/tasks/uipath-maestro-case/_shared/sdd_check.py‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
#!/usr/bin/env python3
22
"""Mechanical check on a case-design ``sdd.md`` (markdown only).
33
4-
Case design (the uipath-planner Case Design Lane) stops at the approved
4+
Case design (the uipath-planner case design path) stops at the approved
55
``sdd.md`` — no caseplan exists yet — so these checks parse the markdown
66
directly to confirm the SDD is sound enough to *deliver downstream* (the
77
build's planning pass trusts it verbatim). Domain sense is graded separately
@@ -112,7 +112,7 @@ def _find_sdd() -> str:
112112

113113

114114
def _rule_token(cell: str) -> str | None:
115-
"""Leading rule keyword from a WHEN cell (``case-entered``, ``adhoc``, …)."""
115+
"""Leading rule keyword from a WHEN cell (``case-entered``, `adhoc`, …)."""
116116
m = re.match(r"`?\s*([a-z][a-z]+(?:-[a-z]+)*)", cell.strip())
117117
return m.group(1) if m else None
118118

‎tests/tasks/uipath-maestro-case/_shared/task_types.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@
2727
SNAPSHOT = HERE / "task_types.json"
2828

2929
# Where the generated guide text lives. One constant, so moving it is one edit.
30-
GUIDE = REPO / "skills" / "uipath-planner" / "references" / "case" / "case-design-layers-guide.md"
30+
GUIDE = REPO / "skills" / "uipath-planner" / "references" / "design" / "case-product-guide.md"
3131
GUIDE_BLOCK_START = "<!-- task-types:not-authorable:start (generated by tests/tasks/uipath-maestro-case/_shared/task_types.py --write-guide; do not edit) -->"
3232
GUIDE_BLOCK_END = "<!-- task-types:not-authorable:end -->"
3333

‎tests/tasks/uipath-maestro-case/_shared/test_task_types.py‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@
2121
import task_types # noqa: E402
2222

2323
REPO = task_types.REPO
24-
CHECKLIST = REPO / "skills" / "uipath-planner" / "references" / "case" / "case-sdd-conformance-checklist.md"
24+
CHECKLIST = REPO / "skills" / "uipath-planner" / "references" / "design" / "case-review-and-conformance-guide.md"
2525
GATES = [
2626
REPO / "tests" / "tasks" / "uipath-maestro-case" / "_shared" / "sdd_check.py",
2727
REPO / "tests" / "tasks" / "uipath-planner" / "_shared" / "sdd_check.py",

0 commit comments

Comments
 (0)