speckit-bugfix-report

Trace bugs to spec artifacts and classify them into structured reports.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-bugfix-report
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-bugfix-report
Source: https://github.com/datamonsterr/mycoai_projects/tree/main/.agents/skills/speckit-bugfix-report
Command: npx skills add https://github.com/datamonsterr/mycoai_projects --skill speckit-bugfix-report

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Capture a bug and trace it back to the relevant spec, plan, and task artifacts.

Core Features & Use Cases

  • Load and reference current feature artifacts (spec.md, plan.md, tasks.md, research.md, data-model.md) to inform debugging.
  • Classify bugs into types (spec gap, spec conflict, implementation drift, untested flow, dependency issue) and associate them with relevant sections.
  • Generate a structured bug report that maps the issue to spec requirements, plan sections, and tasks, ready for patch and verification workflows.

Quick Start

Describe the bug in plain language to produce a structured bug report.

Frequently Asked Questions about speckit-bugfix-report

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

FAQPage Schema
How do I trace a bug back to spec and plan artifacts?

Bug classification categorizes issues into spec gap, spec conflict, implementation drift, untested flow, or dependency issue. By mapping bugs to spec requirements and task plans, it identifies whether the problem stems from missing specs or execution drift.

Does this bug tracing workflow require a .specify directory?

Yes, this bug tracing workflow requires a .specify/ directory with a current feature directory. It relies on reading existing artifacts such as spec.md, plan.md, tasks.md, research.md, and data-model.md to establish traceability for accurate bug reporting.

What is the best way to generate a structured bug report for a spec-kit project?

The best way to generate a structured bug report for a spec-kit project is to input a plain language bug description. The system cross-references feature artifacts to produce a report with artifact traceability and type classification ready for patch workflows.

Why should I classify bugs as implementation drift versus spec conflict?

You should classify bugs as implementation drift versus spec conflict to isolate root causes. Spec conflict indicates contradictory requirements within artifacts, while implementation drift shows the code diverging from the defined spec, guiding targeted debugging and patching.