pbi-escalation-handler

Resolve escalated Product Backlog Items by analyzing pipeline state and review evidence.

15|5|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/sohei56/maul-team --skill pbi-escalation-handler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pbi-escalation-handler
Source: https://github.com/sohei56/maul-team/tree/main/skills/pbi-escalation-handler
Command: npx skills add https://github.com/sohei56/maul-team --skill pbi-escalation-handler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps Scrum Masters handle stalled or failed Product Backlog Item pipelines without losing auditability, worktree state, or clear ownership of the next decision.

Core Features & Use Cases

  • Escalation Triage: Reads PBI state, review findings, metrics, and escalation reasons to select the appropriate response.
  • Recovery Routing: Coordinates retries, holds, blocks, cancellations, developer follow-up, and product-owner decisions with status and state resets.
  • Audit and Communication: Records escalation resolutions, preserves relevant worktrees, updates backlog state, and routes human or agent-mode decisions through the correct channel.
  • Use Case: When a PBI reaches its maximum review rounds or encounters a merge conflict, use this Skill to inspect the evidence, recommend the safest recovery path, and update the Scrum pipeline consistently.

Quick Start

Ask the skill to process the escalated PBI notification for the specified PBI, review its state and latest evidence, apply the response matrix, and record the resolution.

Frequently Asked Questions about pbi-escalation-handler

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

FAQPage Schema
How do I resolve escalated Product Backlog Items that failed during the Scrum pipeline?

Handle PBI escalation by inspecting the pipeline state, review findings, and metrics to apply a response matrix that routes retries, holds, or developer follow-ups while preserving worktrees and audit records.

What is the best way to triage a merge conflict or reviewer failure for a stalled backlog item?

Triage merge conflicts and reviewer failures by reading the PBI state and review evidence to recommend recovery routing, coordinating status resets, and routing human or agent-mode decisions through the correct channel.

Can I use this approach to manage external dependency blocks in my backlog?

Manage external dependency blocks by analyzing the PBI state and escalation reasons to apply recovery routing, coordinate holds, and record the resolution while preserving worktrees and audit trails.

Does PBI escalation handling work with standard Scrum workflows involving maximum review rounds?

Yes, it applies to Scrum workflows by inspecting pipeline state and review evidence when PBIs reach maximum review rounds, applying recovery routing for retries or product-owner decisions while maintaining audit records.

When should I not use automated escalation routing for unclear requirements?

Avoid automated escalation routing for unclear requirements lacking review evidence, as the process depends on analyzing metrics and findings to route product-owner decisions and preserve auditability through correct channels.

How do I ensure auditability when resetting the state of a failed Product Backlog Item?

Maintain auditability when resetting failed PBIs by recording escalation resolutions, preserving worktrees, updating backlog state, and routing decisions through correct channels to avoid losing ownership of the next step.