skills.rest
venikman
venikmanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

workflow/escalate-to-human

Records session escalations with reason, severity, and audit trail for human review.

Updated Jan 11, 2026
Search Tags:#workflow#telemetry#U.Work#escalate#human-review#session-issues
One-click install
npx skills add https://github.com/venikman/fpf-foundry --skill workflow-escalate-to-human
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workflow/escalate-to-human
Source: https://github.com/venikman/fpf-foundry/tree/main/design/skills/workflow/escalate-to-human
Command: npx skills add https://github.com/venikman/fpf-foundry --skill workflow-escalate-to-human

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill records and routes session issues that require human review, capturing severity, target, and related artifacts for auditable escalation.

Core Features & Use Cases

  • Structured escalation: Create a recorded escalation for a session issue with context, reason, and severity.
  • Deterministic logging: Uses a deterministic escalation index per session to aid auditability.
  • U.Work integration: Emits a work log when telemetry/log-work is available for traceability.

Quick Start

Use the escalation tool to create a new escalation record by supplying required inputs: context, session_id, and reason. Example: provide context=AgentWorkflow, session_id=AW-0006, reason="Policy conflict detected", severity=high, target=human.

Frequently Asked Questions about workflow/escalate-to-human

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I escalate a session issue to a human reviewer?▼

You escalate a session issue by supplying context, session_id, and reason to the escalation tool, optionally adding severity and target. This creates a recorded escalation routing the issue to a human reviewer.

What is deterministic escalation indexing for session issues?▼

Deterministic escalation indexing assigns a unique, reproducible index to each session issue escalation. This mechanism aids auditability by ensuring every human review request is tracked consistently within its bounded context.

How does U.Work telemetry logging work with human review escalations?▼

U.Work telemetry logging emits a work log record when the telemetry/log-work component is available. This provides end-to-end traceability for the human review escalation by capturing the routed session issue details.

Can I capture severity and artifacts when routing session issues to human review?▼

Yes, you can capture severity, target, artifacts, decisions, and notes when creating an escalation. Supplying these inputs ensures the human reviewer receives full auditable context regarding the session issue.

When should I use a structured escalation process for session issues?▼

Use a structured escalation process when a session issue requires human review and auditable routing. It is necessary when you need to record context, severity, and related artifacts for a deterministic, traceable human intervention.

Related Skills

Explore More Software Engineering Skills→
venikmanvenikman

governance/start-agent-session

Create deterministic agent session records with validated paths and optional U.Work logging.

Community
Advanced
venikmanvenikman

design/init-context

Create bounded context skeletons with standard subdirectories and README under runtime/contexts.

Community
Intermediate
venikmanvenikman

governance/handoff-to-agent

Record structured YAML handoff artifacts between agent roles within a session.

Community
Basic
mituso89mituso89
2

m-executing-plans

Execute development plans task by task through human-issued commands.

Community
Advanced