Name: u01677-human-approval-routing-for-legal-and-policy-workflows
Author: zwright8

Imported from zwright8/OpenClaw-Code (skills/generated/1677-human-approval-routing-for-legal-and-policy-workflows/SKILL.md). Install upstream with npx skills add zwright8/OpenClaw-Code --skill 1677-human-approval-routing-for-legal-and-policy-workflows. Copyright stays with the author.

Human Approval Routing for legal and policy workflows

Why This Skill Exists

Use human approval routing in legal and policy workflows with emphasis on safety, dignity, equity, and long-term societal benefit.

When To Use

Use this skill when the request explicitly needs "Human Approval Routing for legal and policy workflows" outcomes in the legal and policy workflows domain.

Step-by-Step Implementation Guide

Define measurable outcomes for Human Approval Routing for legal and policy workflows, including baseline and target metrics for legal and policy workflows.
Specify structured inputs/outputs for human approval routing and validate schema contract edge cases.
Implement the core human approval routing logic with deterministic scoring and reproducible execution traces.
Integrate orchestration policy, routing, approval gates, retries, and rollback for autonomous execution.
Run unit, integration, simulation, and regression suites for Human Approval Routing for legal and policy workflows under pro-humanity impact conditions.
Roll out behind a feature flag, monitor telemetry, and refine thresholds using observed operational outcomes.

Required Deliverables

Capability contract: input schema, deterministic scoring, output schema, and failure modes.
Runtime profile: generalist-engine using human approval routing to produce human-approval-routing-artifact-legal-and-policy-workflows.
Orchestration integration: legal-and-policy-workflows:generalist-engine routing, approval gates, retries, and rollback controls.
Validation evidence: unit, integration, simulation, regression-baseline suites and rollout telemetry.

Operational Runbook

Preflight

Validate mission scope, contracts, and required inputs.
Verify feature flag posture, dependencies, and approval prerequisites.

Execution

Execute human approval routing workflow with deterministic scoring and trace capture.
Track posture transitions and preserve reproducible evidence artifacts.

Recovery

Apply rollback strategy if posture is critical or guardrails fail.
Escalate blocked execution to oversight with incident packet and trace references.

Handoff

Publish outcome report, scorecard, and telemetry links.
Queue follow-up tasks for unresolved risks, approvals, or optimization work.

Guardrails

[quality] Require unit and integration validations before promoting Human Approval Routing for legal and policy workflows. -> run-validation:unit+integration+simulation+regression-baseline
[reliability] Trigger rollback on critical posture or repeated failures. -> rollback:rollback-to-last-stable-baseline
[compliance] Require policy and approval gates prior to autonomous deployment. -> approval-gates:policy-constraint-check+human-impact-review
[safety] Block production action when risk posture is critical until human oversight review. -> open-incident:human-oversight

Install u01677-human-approval-routing-for-legal-and-policy-workflows and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "zwright8-openclaw-code-1677-human-approval-routing-for-l-464eae", "kind": "skill", "name": "u01677-human-approval-routing-for-legal-and-policy-workflows", "description": "Build and operate the \"Human Approval Routing for legal and policy workflows\" capability for legal and policy workflows. Use when this exact capability is required by autonomous or human-guided missions.", "publisher": "zwright8", "version": "1.0.0", "capabilities": { "domains": [ "general" ], "tags": [ "skill-md", "github" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Build and operate the \"Human Approval Routing for legal and policy workflows\" capability for legal and policy workflows. Use when this exact capability is required by autonomous or human-guided missions." ], "primary": false, "metadata": { "source": { "provider": "github", "repository": "https://github.com/zwright8/OpenClaw-Code", "path": "skills/generated/1677-human-approval-routing-for-legal-and-policy-workflows/SKILL.md", "ref": "ec1b3b08616195dbe709f116bcfc092c009bb753", "url": "https://github.com/zwright8/OpenClaw-Code/blob/ec1b3b08616195dbe709f116bcfc092c009bb753/skills/generated/1677-human-approval-routing-for-legal-and-policy-workflows/SKILL.md", "key": "zwright8/OpenClaw-Code/skills/generated/1677-human-approval-routing-for-legal-and-policy-workflows/SKILL.md" } }, "instructions": "# Human Approval Routing for legal and policy workflows\n\n## Why This Skill Exists\nUse human approval routing in legal and policy workflows with emphasis on safety, dignity, equity, and long-term societal benefit.\n\n## When To Use\nUse this skill when the request explicitly needs \"Human Approval Routing for legal and policy workflows\" outcomes in the legal and policy workflows domain.\n\n## Step-by-Step Implementation Guide\n1. Define measurable outcomes for Human Approval Routing for legal and policy workflows, including baseline and target metrics for legal and policy workflows.\n2. Specify structu", "cost": { "context_tokens": 734 } }

u01677-human-approval-routing-for-legal-and-policy-workflows

About