---
title: "windbg"
description: "Debug Windows dumps, live user-mode/kernel targets, and time travel traces via WinDbg."
canonical: https://agentpluginsdirectory.com/plugins/windbg
last-updated: 2026-10-21
---

# windbg
Debug Windows dumps, live user-mode/kernel targets, and time travel traces via WinDbg.
- Slug: windbg
- Publisher: Sean Fausett
- Repository: https://github.com/gitfool/kiro-dungeon
- Manifest: windbg/plugin.json
- Version: 2610.1416.3137
- License: MIT
- Category (editorial): code-review
- Skills: 2 (msrc-patch-diff, windbg-debugging)
- MCP servers: 1 (windbg)
- Stars: 0
- Repository created: 2026-08-21
- Repository last pushed: 2026-10-21
- Publisher type: User
- Listing: https://agentpluginsdirectory.com/plugins/windbg
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What windbg does, in the publisher's words

Packages the windbg-mcp server and its windbg-debugging skill as a Kiro power, so they install in one step and the skill activates on keyword.

windbg-mcp wraps WinDbg/DbgEng for four kinds of Windows debugging: dump analysis (crash, hang, or snapshot, user-mode and kernel), live user-mode debugging, kernel debugging, and Time Travel Debugging (TTD) of.run traces. The windbg-debugging skill knows how to drive it, with playbooks for setup, dump triage, live/kernel debugging, heap/pool walking, driver IOCTL discovery, and TTD. See the windbg-mcp README for more details.

windbg-mcp already ships an Agent Skill and an MCP server, both formats Kiro implements directly. This power is a thin wrapper:

- mcp.json declares the windbg server (agent-plugins form).
- skills/windbg-debugging/ is a near-verbatim mirror of the upstream skill.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/gitfool/kiro-dungeon/HEAD/windbg/README.md

## Skills

- msrc-patch-diff
- windbg-debugging: Drive WinDbg/DbgEng via the `windbg` MCP server to debug Windows crash dumps, live user-mode and kernel targets, and Time Travel Debugging (.run) traces. Use when analyzing a.dmp, attaching to a process or the kernel, or recording/navigating/analyzing a TTD trace.

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- windbg: transport: stdio; command: windbg-mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.