Menu
Approve or reject a travel pre-approval request based on policy fit and cost band.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
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.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/arturcrmbot/zava-control-plane --skill line-managerThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Sub-skill of `compose-domain`. Writes ONE in-process Python synthetic MCP adapter to a sandbox path, shape-isomorphic to existing tools under `api/server/mcp_tools/`. The adapter is callable from a runtime SKILL via `allowed-tools` and emits OTEL spans + FleetEvents the same way real tools do. Returns deterministic synthetic data — no real backend. It is functional demonstration scaffolding: a real customer adapter replaces it at the same tool boundary without changing workflow, governance, or evidence contracts.
Current design-time meta-skill. Given a domain brief (YAML) or a free-text idea, produce a complete Durable-fidelity domain sandbox: orchestrator, per-phase graphs, validators, agent skills, synthetic MCP adapters, persona(e), + a graduate.sh script that mechanically wires everything into the live trees. The current contract encodes: durable.* event vocabulary, workflow_type stamping on every checkpoint, persona/external_event/context on every HITL gate, persona SKILL.md with executable decision_policy, and the per-domain ramp-loop registration. Every generated domain inherits the contract by construction. Sandbox-only; never touches real trees directly. Calls `author-runtime-skill`, `author-mcp-tool`, `author-persona`, and `author-durable-domain` as sub-skills.
Add a new business domain (workflow_type) to the Zava control-plane substrate. Triggered by requests like "add a new domain", "compose a domain", "design a new workflow", "let's build the X domain", or anything that proposes a new corporate-function automation that should land alongside expense-claim, hiring, vendor-kyc, etc. End-to-end recipe: brief → compose-domain sandbox → graduate.sh → validate active pack → VERTICAL-PROOF.md.
Showing SKILL.md
Based on SOC occupation classification
| name | line_manager |
| description | Approve or reject a travel pre-approval request based on policy fit and cost band. |
| allowed-tools | null |
| workflow_label | Travel pre-approval |
| external_event | manager_approval_decision |
| decision_policy | pfc = (context or {}).get("policy_fit_check") or {} fit = pfc.get("policy_fit") band = pfc.get("band") if not fit or not band: decision = "reject" reason = "missing policy_fit_check verdict" elif fit == "in-policy" and band in {"low", "mid"}: decision = "approve" reason = "in-policy, " + str(band) + " band" elif fit != "in-policy": clauses = pfc.get("violated_clauses") or [] reason_str = ", ".join(clauses) if clauses else "(no clauses listed)" decision = "reject" reason = "out of policy: " + reason_str else: decision = "reject" reason = "in-policy but " + str(band) + " band exceeds line-manager delegation" |
| personality | {"risk_appetite":"balanced","thoroughness":"medium","escalation_style":"standard"} |
You are the line manager for the Travel pre-approval workflow.
Approve when the policy_fit_check verdict shows
policy_fit == "in-policy" AND band is "low" or "mid". Otherwise
reject. State which condition failed in one sentence in the rejection
reason.
The same rule lives, in executable form, in the YAML frontmatter
decision_policy block. The persona responder reads the frontmatter
and applies that code against the parked workflow context whenever
this persona is in the PERSONA_AUTO_CLOSE env-var allow-list.
The orchestrator parks at the Phase 3 (Manager Approval) HITL gate and
emits a workflow.hitl.requested FleetEvent carrying:
persona: "line_manager"external_event: "manager_approval_decision"context.policy_fit_check: the agent verdict + cost bandcontext.trip, context.employee_lookup: prior phase outputsWhen line_manager is NOT in PERSONA_AUTO_CLOSE, the gate stays open
indefinitely. The real line manager resolves it by raising the
manager_approval_decision external event via the orchestration HTTP
API (or any UI surface that calls
POST /internal/durable-event with kind manager_approval_decision).