workflow/resolve-escalation

Record human escalation resolutions with decision, resolver, and notes.

Updated Jan 11, 2026

Search Tags:#workflow #telemetry #resolve #escalation #decision-record #U.Work #audit-trace

Ready to run

npx skills add https://github.com/venikman/fpf-foundry --skill workflow-resolve-escalation

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: workflow/resolve-escalation
Source: https://github.com/venikman/fpf-foundry/tree/main/design/skills/workflow/resolve-escalation
Command: npx skills add https://github.com/venikman/fpf-foundry --skill workflow-resolve-escalation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured way to record formal resolutions for human escalations, preserving the original escalation record while capturing the final decision.

Core Features & Use Cases

Record a resolution for a given escalation_id with a formal decision (resolved, needs-review, blocked) and optional notes.
Preserve original data by not modifying the escalation record, while storing the resolution as a separate artifact.
Audit-ready logging emits a U.Work entry when telemetry/log-work is available to support traceability.

Quick Start

Invoke the workflow with required inputs: context, escalation_id, and decision. Optional fields such as resolved_by and notes can be supplied to enrich the resolution record.

Frequently Asked Questions about workflow/resolve-escalation

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

FAQPage Schema

How do I record a resolution for a human escalation with an audit trail?▼

To record an escalation resolution, provide a bounded context, escalation_id, and a formal decision (resolved, needs-review, or blocked). The system writes a deterministic resolution file and emits a U.Work log entry for audit traceability.

What decisions are supported when resolving a workflow escalation?▼

Workflow escalation resolutions support three formal decisions: resolved, needs-review, and blocked. You can enrich any of these decisions with optional resolver information and notes to provide context for the audit trace.

How does an audit trace work for escalation resolution records?▼

Audit traces are generated by writing a timestamped resolution file under runtime/contexts/<context>/escalations/ and emitting a U.Work telemetry log when available, preserving the original escalation record without modification.

Can I add notes to an escalation resolution without modifying the original escalation record?▼

Yes, you can add optional notes and resolver details to a resolution. The original escalation record is preserved entirely, while the resolution is stored as a separate markdown artifact alongside it.

Do I need a telemetry logger to use an escalation resolution workflow?▼

No, a telemetry logger is not required to record the resolution file. However, emitting a U.Work log entry for full audit traceability requires telemetry or log-work capabilities to be available in the environment.

What is the best way to handle blocked or needs-review decisions in a human escalation workflow?▼

Handling blocked or needs-review decisions involves invoking the resolution workflow with the specific decision type and optional notes. This formally captures the current state in a resolution file and logs the decision for traceability.