What should I do if my tasks are blocked by dependencies?

The skill suggests four strategies: reordering tasks, splitting tasks into smaller units, using mocking/stubbing, or defining clear interfaces for parallel development.

How does it handle spec-reality divergence?

It provides three specific options: updating the spec for minor deviations, performing a redesign for major shifts, or adjusting the requirements for fundamental technical issues.

Which AI tools is this skill compatible with?

It is designed for use with Claude Code, Cursor, VS Code, and Windsurf as part of the Kiro IDE system prompts.

Can this skill help with technical debt?

Yes, it offers specific strategies such as Refactor-First, Parallel Track, or Incremental Improvement to manage debt while still delivering new features.

What is the Troubleshooting skill used for?

It helps AI assistants and developers diagnose and fix common hurdles like unclear requirements, dependency blocks, and failing tests during the feature implementation process.

Spec-Driven Troubleshooting

Name: Spec-Driven Troubleshooting
Author: jasonkneen

byjasonkneen

•

420

セキュリティとテスト

Diagnoses and resolves common development roadblocks during spec-driven implementation and feature delivery.

概要

This skill provides a comprehensive framework for identifying and overcoming technical hurdles encountered during the software development lifecycle. Designed specifically for spec-driven development (SDD), it offers actionable strategies for handling discrepancies between specifications and reality, managing complex task dependencies, clarifying ambiguous requirements, and addressing performance bottlenecks. Whether you are dealing with failing tests, integration errors, or scope creep, this guide ensures your implementation stays on track by providing structured resolution paths, preventative measures, and specific debugging strategies for the Kiro IDE ecosystem.

主な機能

420 GitHub stars
Dependency Management: Techniques for reordering, splitting, or mocking tasks to unblock development progress.
Integration & Testing Support: Specialized debugging paths for flaky tests, complex mock setups, and cross-environment integration failures.
Spec-Reality Divergence Resolution: Structured strategies for updating specs or redesigning when code doesn't match initial assumptions.
Technical Debt & Performance Optimization: Practical approaches for refactoring legacy code and profiling database or network bottlenecks.
Requirement Clarification: A step-by-step process for analyzing and resolving ambiguous or conflicting project requirements during coding.

ユースケース

Unblocking a development sprint where multiple tasks are stuck in a circular dependency loop.
Resolving architectural mismatches when a third-party API implementation differs from what was planned in the specification.
Systematically identifying and fixing performance regressions or memory leaks during the implementation phase.

概要

主な機能

420 GitHub stars
Dependency Management: Techniques for reordering, splitting, or mocking tasks to unblock development progress.
Integration & Testing Support: Specialized debugging paths for flaky tests, complex mock setups, and cross-environment integration failures.
Spec-Reality Divergence Resolution: Structured strategies for updating specs or redesigning when code doesn't match initial assumptions.
Technical Debt & Performance Optimization: Practical approaches for refactoring legacy code and profiling database or network bottlenecks.
Requirement Clarification: A step-by-step process for analyzing and resolving ambiguous or conflicting project requirements during coding.

ユースケース

Unblocking a development sprint where multiple tasks are stuck in a circular dependency loop.
Resolving architectural mismatches when a third-party API implementation differs from what was planned in the specification.
Systematically identifying and fixing performance regressions or memory leaks during the implementation phase.