speckit-bugfix-verify

Verify spec-kit artifacts for cross-referenced bugfix patches and traceability.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams ensure that bugfix patches remain aligned across spec artifacts (spec.md, plan.md, tasks.md) and corresponding bug reports, preventing drift and missed changes.

Core Features & Use Cases

  • Validates that new requirements in spec.md have corresponding plan or task coverage.
  • Checks that bug reports exist, patch notes are present, and statuses align with expected workflow.
  • Ensures reference integrity and consistent annotations across artifacts to support reproducible verification.

Quick Start

Provide a bug ID to verify a specific patch, or "all" to run a full project-wide check.

Frequently Asked Questions about speckit-bugfix-verify

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

FAQPage Schema
How do I verify bugfix patch consistency across spec.md, plan.md, and tasks.md?

Verify bugfix patch consistency by reading the .specify/ directory and validating that new requirements in spec.md have corresponding plan or task coverage. This ensures bugfix patches are consistently applied and prevents drift across spec artifacts.

What is cross-artifact traceability for bug reports and spec-kit project structures?

Cross-artifact traceability for spec-kit project structures ensures new requirements reference existing bug reports and have clear acceptance criteria. It enforces reference integrity across spec.md, plan.md, and tasks.md to support reproducible verification.

How do I check for missing patch dates and unmatched bug IDs in spec artifacts?

Check for missing patch dates and unmatched bug IDs by running a full project-wide verification on the .specify/ directory. The process reports precise failures for any missing patch dates, unmatched bug IDs, or duplicated requirements across artifacts.

Can I validate a specific bugfix patch without checking the entire project?

Yes, you can validate a specific bugfix patch by providing a specific bug ID instead of running a full project check. This targets the verification to ensure the corresponding bug report exists, patch notes are present, and statuses align with the expected workflow.

Why does spec-kit artifact validation report failures for duplicated requirements?

Spec-kit artifact validation reports failures for duplicated requirements to enforce consistent annotations and maintain reference integrity across spec.md, plan.md, and tasks.md. This prevents drift and ensures missed changes are caught during bugfix patch verification.