skills.rest
HHU3637kr
HHU3637krCOMMUNITY
Explore all skills by this author →
GitHub

spec-debug

Create debug documents and fix summaries for Spec execution issues.

140|20|Updated Jan 8, 2026
Search Tags:#debugging#documentation#spec#workflows#issue-tracking#team-collaboration
One-click install
npx skills add https://github.com/HHU3637kr/skills --skill spec-debug
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: spec-debug
Source: https://github.com/HHU3637kr/skills/tree/main/spec-debug
Command: npx skills add https://github.com/HHU3637kr/skills --skill spec-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

诊断并修复在 Spec 执行过程中出现的问题，确保变更不会影响已确认的 plan.md，通过创建独立的诊断文档（debug-xxx.md）和修复总结（debug-xxx-fix.md）来保持溯源性和闭环。

Core Features & Use Cases

  • 闭环协作：从 bug 发现到诊断再到修复，形成可追溯的工作流。
  • 模板驱动诊断：提供标准化的 debug-xxx.md 与 debug-xxx-fix.md 结构，确保信息完整。
  • 与计划文档关联：诊断结果与 plan.md 保持一致性，便于审计与回溯。

Quick Start

遇到 Spec 运行问题时，按照工作流程创建 debug-001.md 诊断文档并通知 TeamLead 进行用户确认。

Frequently Asked Questions about spec-debug

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

FAQPage Schema
How do I debug issues during Spec execution without altering the confirmed plan?▼

To debug Spec execution issues without altering the plan, create dedicated debug-xxx.md diagnostic documents and debug-xxx-fix.md summaries. This isolates troubleshooting, ensuring changes remain traceable and do not corrupt the original plan.md.

What is a closed-loop debugging workflow for collaborative Spec execution?▼

A closed-loop debugging workflow for collaborative Spec execution tracks an issue from detection through diagnosis to repair. It uses structured debug templates and plan linkage to ensure closed-loop verification and traceability across multiple team roles.

How do I structure issue-tracking documents for multi-role team collaboration?▼

Structure issue-tracking documents for team collaboration by applying standardized debug-xxx.md and debug-xxx-fix.md templates. This template-driven approach ensures information completeness, links results back to plan.md, and maintains auditability.

Does Spec execution debugging require TeamLead confirmation for fixes?▼

Yes, Spec execution debugging requires TeamLead confirmation for fixes. When you encounter a Spec issue and create a debug-001.md diagnostic document, you must notify the TeamLead to obtain user confirmation before proceeding with controlled changes.

When should I use dedicated debug documents instead of inline code comments?▼

Use dedicated debug documents instead of inline comments when resolving Spec execution issues requiring traceability and closed-loop verification. This maintains documentation discipline, ensures plan linkage, and supports controlled changes across multiple workflow stages.

Related Skills

Explore More Software Engineering Skills→
samjhechtsamjhecht
4

initialize-governance

Generate Constitution, Roadmap, and process documentation templates for project governance.

Community
Advanced
novel-jpnovel-jp

learn-se-issue

Create a complete issue lifecycle exercise for tracking bugs from discovery to closure.

Official
Intermediate
PriyanshKuniyalPriyanshKuniyal

context-driven-development

Automate creation, validation, and synchronization of project context artifacts.

Community
Advanced
hq-opensourcehq-opensource
7

gsd-debug

Document software bug investigations in .planning/debug/{issue-id}.md files.

Official
Advanced