debug

Diagnose and repair software bugs through a six-phase workflow with specialized agents.

1|1|Updated Jan 21, 2026
One-click install
npx skills add https://github.com/kenkenmain/ken-cc-plugins --skill debug-kenkenmain
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/kenkenmain/ken-cc-plugins/tree/main/plugins/ants/skills/debug
Command: npx skills add https://github.com/kenkenmain/ken-cc-plugins --skill debug-kenkenmain

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and repairs bugs in a software project by orchestrating a structured, six-phase workflow that runs in a stateless, direct-dispatch mode with specialized agents.

Core Features & Use Cases

  • Six-phase workflow (D0-D5) coordinates dedicated agents for exploration, proposal, aggregation, implementation, adversarial review, and shipping.
  • Stateless direct dispatch avoids external state files and enables flexible, repeatable bug-fix sessions.
  • Parallel agent roles (bug-scouts, solution-proposers, sentinels, nurse, drone) speed up discovery, validation, and delivery.
  • Use Cases: ideal for complex bug fixes requiring joint evaluation, layered verification, and comprehensive documentation before deployment.

Quick Start

Provide a bug report and run the debug command to trigger the six-phase pipeline.

Frequently Asked Questions about debug

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

FAQPage Schema
What is a parallel bug-fix pipeline with adversarial review?

A parallel bug-fix pipeline with adversarial review coordinates specialized agents across six phases—investigation, proposal, aggregation, implementation, review, and documentation—to systematically diagnose and repair complex software bugs before shipping.

How do I fix complex software bugs using a structured workflow?

Fix complex software bugs by triggering a six-phase pipeline: provide a bug report to initiate stateless direct dispatch, which routes the issue through parallel agents for investigation, implementation, and layered verification before final deployment.

Does stateless direct dispatch require external state files for bug tracking?

No, stateless direct dispatch explicitly avoids external state files like state.json. This enables flexible, repeatable bug-fix sessions by coordinating the workflow and specialized agents without relying on persistent state tracking.

Can I use parallel processing for software maintenance and layered verification?

Yes, parallel processing applies to software maintenance by assigning bug-scouts, solution-proposers, and sentinels to run concurrently. This accelerates discovery, validation, and layered verification across correctness, security, performance, and style.

When do I need an adversarial review workflow for software maintenance?

You need an adversarial review workflow for software maintenance when complex bug fixes require joint evaluation and comprehensive documentation. It ensures layered verification by dedicated sentinels before any code changes are shipped.

What are the limitations of using a stateless dispatch pipeline for bug fixes?

The stateless dispatch pipeline requires strict adherence to six defined phases and specialized agent roles. It is designed for complex bug fixes needing comprehensive documentation, so simple patches may not warrant the full workflow overhead.