- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add microsoft/win-dev-skills --skill windbg-kernel-irp-lifecycle-triage -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add microsoft/win-dev-skills --skill windbg-kernel-irp-lifecycle-triage -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add microsoft/win-dev-skills --skill windbg-kernel-irp-lifecycle-triage -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add microsoft/win-dev-skills --skill windbg-kernel-irp-lifecycle-triage -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/microsoft/win-dev-skills/tree/HEAD/plugins/windbg/skills/windbg-kernel-irp-lifecycle-triageFrom the publisher
Load windbg-diagnostic-method first if it is not already loaded in this
conversation, and apply it throughout for evidence ranking, hypothesis testing,
confidence calibration, independent review, and report validation. This skill
adds the bug-family-specific commands and evidence requirements.
Investigate I/O Request Packets in a kernel dump or authorized live kernel
session. Examples include 0x9F power failures and hangs where progress
depends on a driver request. Apply the parameter table for the specific
bugcheck subtype rather than assuming every 0x9F identifies the same object.
For 0x9F with P1 equal to 3, P4 is the blocked IRP. Inspect that directly
before running a system-wide search.
!analyze -v
!irp <irp-address>
When no request address is known and the dump has the required pool data:
!irpfind
!irpfind can be expensive in a live session and incomplete in a limited dump.
Use supported filters where appropriate. No result does not prove there are
no outstanding requests.
Record the major/minor operation, current stack location, device/driver stack, completion routine, pending flags, cancellation state, and any relevant thread. Use the available device stack and driver source to establish which component is expected to advance or complete the request.
Do not identify an offending driver solely by the last name printed in the IRP stack. A completion routine, downstream dependency, or framework-owned request may change the responsible path.
Preserve evidence between skills; avoid repeatedly handing the same unchanged IRP back and forth.
WDM and WDF have different ownership APIs. Do not transplant a raw WDM completion/cancel pattern into a framework-owned request without checking its contract. This skill establishes evidence; it is not a complete I/O protocol reference or a decoder for every power subtype.
Name the operation, current owner/dependency, and supported protocol violation or stalled path. Test normal completion, concurrent cancellation, removal, power transitions, and shutdown where relevant. If history is missing, propose an approved instrumented test using the verifier skill rather than inventing which driver lost the completion.
Follow FEEDBACK.md and report only reviewed, sanitized feedback to
WinDbg-Feedback.
Include windbg-kernel-irp-lifecycle-triage and the package version from plugin.json; no
automatic kernel dump or request-content upload.
Use when kernel evidence shows stalled I/O, a power IRP, or completion/cancellation misuse; inspect request state and driver ownership. Not for interpreting an empty IRP search in a limited dump as pr
---name: windbg-kernel-irp-lifecycle-triagedescription: Use when kernel evidence shows stalled I/O, a power IRP, or completion/cancellation misuse; inspect request…---# plugins/windbg/skills/windbg-kernel-irp-lifecycle-triage/SKILL.mdOverview
Use when kernel evidence shows stalled I/O, a power IRP, or completion/cancellation misuse; inspect request state and driver ownership. Not for interpreting an empty IRP search in a limited dump as proof of healthy I/O.
FAQ
Download plugins/windbg/skills/windbg-kernel-irp-lifecycle-triage/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/microsoft/win-dev-skills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.