Menu
Activate when designing any new case stage, child case, or grandchild case. Defines the six case-shape patterns Maestro Case must demonstrate.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Offline, credential-free knowledge + static validators for UiPath Maestro Case footguns. Explain cryptic error codes (400300, 160009, ...) and lint caseplans, spawn inputs, and Data Fabric specs in CI — no UiPath login. Use when authoring, debugging, or reviewing UiPath Maestro Case / Data Fabric / Action Center work.
Cross-runtime skill optimizer. Use this skill when the user wants to package an Agent Skill so it runs in both Claude Code and OpenAI Codex from a single portable source. Also use when the user wants to import an existing skill (Claude Code or Codex) into the portable format, build/emit for any runtime, install a skill into Claude Code or Codex, or troubleshoot why a skill behaves differently across runtimes.
Use when the user wants to package a skill so it runs in both Claude Code and Codex from one source, import an existing skill into the portable format, install to Claude or Codex, or troubleshoot cross-runtime drift.
Structure long-running Claude Code sessions on this Python project so the agent iterates for hours instead of stopping after one pass. Use when the user mentions "long-running session", "multi-hour run", "agent keeps stopping", "agent finishes too early", "headless run", "tmux session", "milestones", "make verify", "fake success", "prevent shortcuts", or asks how to set up hooks, a verification gate, or an operating contract for an autonomous coding agent.
Activate when the BAA Boundary Reasoner Agent runs or when a regulatory inquiry hits multiple affected provider customers. Teaches how to reason about a single regulatory inquiry against multiple differing BAA terms.
Activate when rehearsing or testing the demo runner. Guides dry-running the 3-minute demo end-to-end against the local stack.
| name | case-shape-patterns |
| description | Activate when designing any new case stage, child case, or grandchild case. Defines the six case-shape patterns Maestro Case must demonstrate. |
Define and enforce the six case-shape patterns that distinguish this Maestro Case demonstration from a BPMN workflow.
The master case goal changes at each reversal. This is not a state machine with predefined transitions — goals emerge from new information.
| Reversal | Goal Before | Goal After |
|---|---|---|
| 1 | Assist isolated customers | Determine if ClearFlow is the vector |
| 2 | Am I the cause? | Strategic bystander posture |
| 3 | (unchanged) | + Per-customer BAA compliance |
| 4 | Strategic posture | Fiduciary conflict resolution |
| 5 | Fiduciary resolution | Co-defendant defense posture |
Participants' roles change as the case evolves. ClearFlow starts as recovery coordinator, becomes conflict-governed intermediary, becomes co-defendant.
Three levels: master → parent → grandchild. The third level emerges only when needed (Reversal 3).
Evidence is shared across cases but access depends on participant role and privilege status. When litigation arrives (Reversal 5), privilege reshuffles and some evidence becomes restricted.
HITL decisions don't follow a fixed sequence. They appear when the case demands them, sometimes reopening previously resolved decisions.
Closed child cases can reopen. Completed stages can re-enter. The IDR Posture child case opens on Day 0, resolves, then reopens on Day 60 with a different posture question.
