troubleshooting
π―Skillfrom jasonkneen/kiro
I apologize, but I cannot confidently infer the specific functionality of a "troubleshooting" Claude Code skill from this README. The README appears to be about spec-driven development methodology ...
Installation
npx skills add https://github.com/jasonkneen/kiro --skill troubleshootingSkill Details
Overview
# Spec-Driven Development Guide
[](https://smithery.ai/skills?ns=jasonkneen&utm_source=github&utm_medium=badge)
A comprehensive guide to systematic feature development using the three-phase spec process: Requirements β Design β Tasks.
Used by
- [@kazini](https://github.com/kazini) in their spec kit https://github.com/kazini/yask-spec-kit
- Amazon in internal presentations: _"Itβs the best stuff I have found on [spec driven development]. I will be sharing links back to your repo with full attribution."_
π§ Navigation Guide
New to spec-driven development? β Start with [Methodology Overview](spec-process-guide/methodology/README.md)
Ready to create your first spec? β Jump to [Process Guide](spec-process-guide/process/README.md)
Looking for examples? β Browse [Examples & Case Studies](spec-process-guide/examples/README.md)
Need templates? β Get [Ready-to-Use Templates](spec-process-guide/templates/README.md)
Working with AI? β Learn [Prompting Strategies](spec-process-guide/prompting/README.md)
π Need detailed navigation? β See [Complete Navigation Index](spec-process-guide/NAVIGATION.md) - Find content by role, problem, or learning style
---
π Complete Table of Contents
π― [Methodology](spec-process-guide/methodology/README.md)
Learn the foundational concepts and philosophy behind spec-driven development
- [Overview](spec-process-guide/methodology/overview.md) - Core concepts and benefits
- [Philosophy](spec-process-guide/methodology/philosophy.md) - Why spec-driven development works
- [When to Use](spec-process-guide/methodology/when-to-use.md) - Decision framework and scenarios
π [Process Guide](spec-process-guide/process/README.md)
Step-by-step walkthrough of the three-phase workflow
- [Requirements Phase](spec-process-guide/process/requirements-phase.md) - Gathering and structuring requirements using EARS
- [Design Phase](spec-process-guide/process/design-phase.md) - Creating comprehensive design documents
- [Tasks Phase](spec-process-guide/process/tasks-phase.md) - Breaking down design into actionable coding tasks
- [Workflow Diagrams](spec-process-guide/process/workflow-diagrams.md) - Visual process flows and decision points
π§ [AI Reasoning](spec-process-guide/ai-reasoning/README.md)
Insights into decision-making frameworks and thought processes
- [Decision Frameworks](spec-process-guide/ai-reasoning/decision-frameworks.md) - How choices are evaluated
- [Thought Processes](spec-process-guide/ai-reasoning/thought-processes.md) - Analysis and prioritization methods
- [Examples](spec-process-guide/ai-reasoning/examples.md) - Real reasoning chains and decision points
π¬ [Prompting Strategies](spec-process-guide/prompting/README.md)
Effective communication techniques for AI collaboration
- [Strategies](spec-process-guide/prompting/strategies.md) - Core prompting approaches
- [Templates](spec-process-guide/prompting/templates.md) - Ready-to-use prompt patterns
- [Best Practices](spec-process-guide/prompting/best-practices.md) - Tips for clear, effective communication
β‘ [Execution Guide](spec-process-guide/execution/README.md)
Practical guidance for implementing features from specs
- [Implementation Guide](spec-process-guide/execution/implementation-guide.md) - Step-by-step execution strategies
- [Quality Assurance](spec-process-guide/execution/quality-assurance.md) - Testing and validation techniques
- [Troubleshooting](spec-process-guide/execution/troubleshooting.md) - Common issues and solutions
π [Resources](spec-process-guide/resources/README.md)
Curated references and learning materials
More from this repository5
I apologize, but I cannot confidently generate a description of the Claude plugin marketplace from this README. The README appears to be about a spec-driven development methodology guide, and does ...
Guides developers through a systematic three-phase process of requirements gathering, design documentation, and task breakdown for more structured and intentional software development.
Generates structured, systematic software requirements using the EARS (Easy Approach to Requirements Syntax) methodology, transforming user needs into precise, actionable specification documents.
Generates comprehensive design documentation by transforming requirements into structured technical design artifacts and architectural diagrams.
Generates optimized AI prompting strategies and templates to improve communication and task specification when working with AI systems.