troubleshooting

Diagnose and resolve spec-to-code implementation issues with structured guidance and checklists.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/bwgz/teambuilder --skill troubleshooting-bwgz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: troubleshooting
Source: https://github.com/bwgz/teambuilder/tree/main/teambuilder-sdd/.claude/skills/troubleshooting
Command: npx skills add https://github.com/bwgz/teambuilder --skill troubleshooting-bwgz

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnose and resolve common problems that arise during spec-driven development and implementation.

Core Features & Use Cases

  • Strategies for handling spec-reality divergence, dependency blocks, unclear requirements, and other execution challenges.
  • Practical templates and checklists to surface gaps, document decisions, and keep work aligned with the original spec.
  • Use cases across design, coding, and testing to prevent rework and accelerate delivery.

Quick Start

Describe a concise triage plan to diagnose and resolve a failing spec-to-implementation gap in your project.

Frequently Asked Questions about troubleshooting

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

FAQPage Schema
How do I fix spec-to-implementation divergence during development?

Spec-to-implementation divergence is resolved by applying structured triage plans to document gaps, replan tasks, and align stakeholders, preventing scope creep. This provides checklists and decision options to keep coding aligned with original requirements.

What is the best way to handle unclear requirements when translating specs into working code?

Handling unclear requirements involves using practical templates and checklists to surface gaps, document decisions, and maintain spec alignment. It offers structured guidance to diagnose execution challenges and prevent rework across design, coding, and testing phases.

How do I unblock dependency issues in spec-driven development?

Dependency blocks in spec-driven development are unblocked by diagnosing execution challenges and applying structured decision options to replan tasks. This approach assesses risks and provides actionable strategies to keep implementation moving forward.

Can I use structured checklists to prevent scope creep during software testing?

Structured checklists can prevent scope creep by documenting decisions and maintaining alignment with the original spec across testing phases. They surface requirement gaps early, accelerating delivery and reducing rework during implementation.

Why does my implementation drift from the original spec during coding?

Implementation drifts from the original spec due to divergence, dependency blocks, and unclear requirements encountered during translation. Diagnosing these issues with structured guidance and risk assessment helps document gaps and realign coding with stakeholder expectations.