defect

Creates structured markdown bug reports with severity and branch context.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/Covcloud-LLC/adhd-workflow --skill defect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: defect
Source: https://github.com/Covcloud-LLC/adhd-workflow/tree/main/skills/defect
Command: npx skills add https://github.com/Covcloud-LLC/adhd-workflow --skill defect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the friction of logging bugs during active development by providing a standardized, low-effort way to record symptoms and hunches without breaking your current focus or forcing you to perform immediate root-cause analysis.

Core Features & Use Cases

  • Frictionless Capture: Quickly logs bug reports with standardized metadata including status, severity, and branch context.
  • Workflow Integration: Automatically detects whether to use a local repository or a centralized backlog metarepo for documentation.
  • Use Case: When you encounter an unexpected error while coding, use this skill to log the symptom and your initial thoughts, allowing you to return to your task immediately while leaving a clear trail for later investigation.

Quick Start

Trigger the defect skill by telling the AI to log a bug about the premium feature failing to refresh after an edit.

Frequently Asked Questions about defect

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

FAQPage Schema
How do I log a bug report in markdown without interrupting my current coding workflow?

You can log bug reports in markdown by quickly capturing symptoms, expected versus actual behavior, and developer hunches. This standardized recording allows you to document the defect immediately and return to your task without performing root-cause analysis on the spot.

How does capturing software defects in a local repository versus a centralized backlog work?

Capturing software defects works by automatically detecting your environment to determine persistence. It implements automated git-based persistence for metarepo configurations while maintaining local file system integrity for standard project structures, organizing the structured markdown files accordingly.

Can I track bug severity and branch context when logging software defects?

Yes, you can track bug severity and branch context. The frictionless capture mechanism logs bug reports with standardized metadata including status, severity, and branch context directly into structured markdown files within your repository.

What is the best way to record unexpected errors and developer hunches for later investigation?

The best way to record unexpected errors is to log the symptom and your initial thoughts into a structured markdown file. This creates a clear trail for future diagnostic workflows, leaving a standardized record of the defect without breaking your current focus.

Does this bug tracking approach require immediate root-cause analysis?

No, this bug tracking approach does not require immediate root-cause analysis. It provides a low-effort way to record symptoms and hunches, allowing you to return to your development task immediately while leaving a clear trail for later investigation.