debug-process

Diagnose process failures and generate a structured Debug Report.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/samurano/ai-brain --skill debug-process
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-process
Source: https://github.com/samurano/ai-brain/tree/main/.agents/skills/debug-process
Command: npx skills add https://github.com/samurano/ai-brain --skill debug-process

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The Skill helps you systematically investigate process and workflow failures, lost tasks, broken workflows, or content desynchronization without guessing fixes.

Core Features & Use Cases

  • Phased debugging approach guiding you through symptom collection, pattern analysis, hypothesis creation, minimal fixes, and verification.
  • References to project-files-schema, log.md, decisions.md, and lessons.md to preserve durable context and learn from issues.
  • Structured Debug Report output that documents the problem, root causes, implemented fixes, verification results, and recommendations.

Quick Start

Describe the failing process and follow the five phases to produce the Debug Report.

Frequently Asked Questions about debug-process

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

FAQPage Schema
How do I debug a stalled process or workflow failure systematically?

To debug a stalled process or workflow failure, apply a phased debugging methodology that guides you through symptom collection, pattern analysis, hypothesis creation, minimal fixes, and verification to produce a structured Debug Report.

What is the best way to find the root cause of lost tasks or desynchronized files?

The best way to find the root cause of lost tasks or desynchronized files is to enforce a structured diagnostic process that analyzes logs and references to pinpoint failures without guessing fixes.

How does structured debugging document root causes and resolutions for content pipelines?

Structured debugging documents root causes for content pipelines by generating a structured Debug Report that records the problem, root causes, implemented fixes, verification results, and recommendations.

Can I use this debugging process for issues across filesystems and task management?

Yes, you can use this debugging process for issues across filesystems and task management, as it is designed to diagnose and resolve complex process or workflow failures across these environments.

Do I need existing log files to diagnose broken workflows with this approach?

Yes, you need existing log files, as the debugging approach references log.md, decisions.md, and lessons.md to preserve durable context and learn from issues during diagnosis.

What are the limitations of guessing fixes for out-of-sync files across governance tasks?

Guessing fixes for out-of-sync files across governance tasks lacks durability and fails to preserve context, whereas a phased debugging methodology systematically resolves issues and updates durable logs.