skills.rest
hilaryosborne
hilaryosborneCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

dl-problem-solving

Diagnose root causes of blocked work and guide resolution steps.

Updated Feb 21, 2026
Search Tags:#problem solving#troubleshooting#blockers#delivery#sprint#impediments
One-click install
npx skills add https://github.com/hilaryosborne/skills --skill dl-problem-solving
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dl-problem-solving
Source: https://github.com/hilaryosborne/skills/tree/main/delivery-lead/dl-problem-solving
Command: npx skills add https://github.com/hilaryosborne/skills --skill dl-problem-solving

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify and resolve blockers that impede the smooth flow of work within a delivery team.

Core Features & Use Cases

  • Blocker Identification: Helps surface and categorize impediments.
  • Root Cause Analysis: Guides the team in understanding the underlying reasons for problems.
  • Resolution Planning: Assists in developing actionable steps to remove blockers.
  • Use Case: A sprint is stalled because a critical API is down. This skill can help the Delivery Lead facilitate a discussion to diagnose the issue, identify who can fix it, and track the resolution.

Quick Start

Use the dl-problem-solving skill to help identify the root cause of the current sprint delay.

Frequently Asked Questions about dl-problem-solving

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

FAQPage Schema
How do I identify and resolve blockers impacting sprint delivery?▼

Root cause analysis for stalled sprints involves facilitating team discussions to diagnose underlying reasons for problems. This structured approach identifies who can fix critical issues and tracks the resolution to restore workflow.

What is the best way to facilitate problem solving when a sprint is stalled?▼

When unforeseen issues impact team velocity, impediment resolution requires categorizing the blockers and diagnosing underlying reasons. Structured questioning guides the team in understanding the root causes and developing actionable resolution steps.

How do I run a root cause analysis for software delivery impediments?▼

Root cause analysis for stalled sprints involves facilitating team discussions to diagnose underlying reasons for problems. This structured approach identifies who can fix critical issues and tracks the resolution to restore workflow.

Can I use structured troubleshooting for delivery roadblocks without external dependencies?▼

Yes, you can facilitate structured troubleshooting for delivery roadblocks without external dependencies. The process requires no specific modules, relying entirely on guided questioning to analyze impediments and plan actionable resolution steps.

Why does team velocity drop when critical dependencies fail during a sprint?▼

Team velocity drops during a sprint when critical dependencies fail because unforeseen issues create impediments that stall progress. Identifying these blockers and diagnosing their root causes is required to guide actionable resolution steps.

Related Skills

Explore More Software Engineering Skills→
devmuslimdevmuslim

impediment-log

Track delivery impediments with ownership, aging alerts, and pattern analysis.

Community
Basic
cody-hutsoncody-hutson

pmo-scrum-master

Facilitate Scrum sprint planning, impediment removal, and team flow monitoring.

Community
Advanced
aiunlocked1412aiunlocked1412
14

agile-coach

Generate sprint planning packages with capacity calculations and ceremony scripts.

Community
Intermediate
lloydchanglloydchang
2

incident-triage-automator

Aggregate alerts from monitoring systems and compute incident severity.

Community
Advanced