<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Troubleshooting | SpecDD</title><link>https://specdd.ai/how-to/troubleshooting/</link><description>Spec-driven development troubleshooting guides for agent setup, editor recognition, CLI installs, Node versions, spec resolution, path references, stale criteria, and plugin or skill installs.</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://specdd.ai/how-to/troubleshooting/index.xml" rel="self" type="application/rss+xml"/><item><title>How to fix an agent that ignores your specs</title><link>https://specdd.ai/how-to/troubleshooting/how-to-fix-an-agent-that-ignores-your-specs/</link><guid>https://specdd.ai/how-to/troubleshooting/how-to-fix-an-agent-that-ignores-your-specs/</guid><description>Fix an agent that ignores SpecDD specs by checking bootstrap setup, agent entrypoint wiring, plugin or skills installation, working directory, content root, and prompt scope.</description></item><item><title>How to fix .sdd files not being recognized or highlighted</title><link>https://specdd.ai/how-to/troubleshooting/how-to-fix-sdd-files-not-being-recognized-or-highlighted/</link><guid>https://specdd.ai/how-to/troubleshooting/how-to-fix-sdd-files-not-being-recognized-or-highlighted/</guid><description>Fix .sdd files not being recognized or highlighted by checking editor plugins, file associations, workspace trust, filename extensions, reloads, and conflicting extensions.</description></item><item><title>How to fix a failing SpecDD CLI install or "command not found"</title><link>https://specdd.ai/how-to/troubleshooting/how-to-fix-a-failing-specdd-cli-install-or-command-not-found/</link><guid>https://specdd.ai/how-to/troubleshooting/how-to-fix-a-failing-specdd-cli-install-or-command-not-found/</guid><description>Fix SpecDD CLI install failures and command not found errors by checking Node, npm or Yarn globals, PATH, shell refresh, package manager output, Docker, and specdd --help.</description></item><item><title>How to fix SpecDD Node version errors</title><link>https://specdd.ai/how-to/troubleshooting/how-to-fix-specdd-node-version-errors/</link><guid>https://specdd.ai/how-to/troubleshooting/how-to-fix-specdd-node-version-errors/</guid><description>Fix SpecDD Node version errors by checking node -v, installing Node.js 22 or newer, avoiding mixed Node environments, and using Docker or another install path when needed.</description></item><item><title>How to resolve ambiguous spec match warnings</title><link>https://specdd.ai/how-to/troubleshooting/how-to-resolve-ambiguous-spec-match-warnings/</link><guid>https://specdd.ai/how-to/troubleshooting/how-to-resolve-ambiguous-spec-match-warnings/</guid><description>Resolve ambiguous SpecDD spec match warnings by fixing case-only same-basename collisions, preferring exact filenames, and renaming specs so tools do not guess.</description></item><item><title>How to fix path references that do not resolve</title><link>https://specdd.ai/how-to/troubleshooting/how-to-fix-path-references-that-do-not-resolve/</link><guid>https://specdd.ai/how-to/troubleshooting/how-to-fix-path-references-that-do-not-resolve/</guid><description>Fix unresolved SpecDD path references by checking explicit prefixes, relative location, content root, moved files, case sensitivity, stale references, and globs.</description></item><item><title>How to debug spec resolution problems</title><link>https://specdd.ai/how-to/troubleshooting/how-to-debug-spec-resolution-problems/</link><guid>https://specdd.ai/how-to/troubleshooting/how-to-debug-spec-resolution-problems/</guid><description>Debug SpecDD resolution problems by tracing the selected content root, ancestor specs, directory specs, same-basename matching, references, globs, and CLI resolve output.</description></item><item><title>How to fix specs that are too vague to be useful</title><link>https://specdd.ai/how-to/troubleshooting/how-to-fix-specs-that-are-too-vague-to-be-useful/</link><guid>https://specdd.ai/how-to/troubleshooting/how-to-fix-specs-that-are-too-vague-to-be-useful/</guid><description>Fix vague SpecDD specs by replacing generic goals with local ownership, observable Must rules, realistic Must not boundaries, scenarios, tasks, and Done when criteria.</description></item><item><title>How to fix a spec that conflicts with a parent spec</title><link>https://specdd.ai/how-to/troubleshooting/how-to-fix-a-spec-that-conflicts-with-a-parent-spec/</link><guid>https://specdd.ai/how-to/troubleshooting/how-to-fix-a-spec-that-conflicts-with-a-parent-spec/</guid><description>Fix a SpecDD child spec that conflicts with a parent spec by reading the inherited chain, applying stricter-wins logic, rewriting invalid tasks, and escalating unsafe changes.</description></item><item><title>How to fix an agent that cannot find the right local spec</title><link>https://specdd.ai/how-to/troubleshooting/how-to-fix-an-agent-that-cannot-find-the-right-local-spec/</link><guid>https://specdd.ai/how-to/troubleshooting/how-to-fix-an-agent-that-cannot-find-the-right-local-spec/</guid><description>Fix an agent that cannot find the right SpecDD local spec by checking working directory, content root, same-basename placement, directory specs, references, and target path.</description></item><item><title>How to fix stale Done when criteria</title><link>https://specdd.ai/how-to/troubleshooting/how-to-fix-stale-done-when-criteria/</link><guid>https://specdd.ai/how-to/troubleshooting/how-to-fix-stale-done-when-criteria/</guid><description>Fix stale SpecDD Done when criteria by comparing current behavior, tasks, tests, and review needs, then updating completion criteria with the code change.</description></item><item><title>How to fix broken SpecDD plugin or skill installs</title><link>https://specdd.ai/how-to/troubleshooting/how-to-fix-broken-specdd-plugin-or-skill-installs/</link><guid>https://specdd.ai/how-to/troubleshooting/how-to-fix-broken-specdd-plugin-or-skill-installs/</guid><description>Fix broken SpecDD plugin or Agent Skills installs by checking install paths, universal skills deployment, scope, reloads, discovery, and smoke-test prompts.</description></item></channel></rss>