specdd-debug
Debug SpecDD Contract Failures
SpecDD projects can fail when implementation, tests, and contracts drift apart. This skill guides Claude, Codex, and Claude Code through focused contract-based debugging.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "specdd-debug" from https://skillstore.io/skills/specdd-specdd-debug.md and its manifest at https://skillstore.io/api/skills/specdd-specdd-debug/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "specdd-debug". A route returns a different error than the SpecDD contract describes.
Expected outcome:
The result identifies the governing contract, explains the drift, applies a narrow implementation fix, and reports the verification outcome.
Using "specdd-debug". A test fails after a spec update.
Expected outcome:
The result separates test drift from implementation drift and recommends the smallest compliant update.
Using "specdd-debug". The requested behavior conflicts with a local spec.
Expected outcome:
The result stops before editing, explains the conflict, and asks for a decision on the contract direction.
Security Audit
SafeAll seven static findings are false positives caused by Markdown inline code in SKILL.md. The reviewed file contains workflow guidance only, with no executable scripts, shell invocation, network access, credential handling, or prompt injection attempt.
Risk Factors
⚙️ External commands (7)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/specdd-specdd-debug/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/specdd-specdd-debug?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/specdd-specdd-debug?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/specdd-specdd-debug/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/specdd-specdd-debug.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
specdd. (2026). specdd-debug security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/specdd-specdd-debug/audits/5BibTeX citation
@techreport{specdd-specdd-specdd-debug-2026,
author = {specdd},
title = {specdd-debug security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/specdd-specdd-debug/audits/5},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "specdd-debug security audit report (audit version 5)"
version: "unspecified"
type: report
authors:
- name: "specdd"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/specdd-specdd-debug/audits/5"
identifiers:
- type: other
value: "skillstore:specdd-specdd-debug:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Fix implementation drift
Compare a failing behavior with the active SpecDD contract and make the smallest compliant code change.
Triage failing tests
Decide whether a failure comes from test drift, implementation drift, ambiguous specs, or missing coverage.
Review contract authority
Confirm the governing bootstrap and spec chain before changing files in a SpecDD project.
Try These Prompts
Use specdd-debug to inspect this failing behavior and identify the governing SpecDD contract before suggesting changes.
Use specdd-debug to reproduce the failure, resolve the effective spec chain, and make the smallest fix within write authority.
Use specdd-debug to decide whether this failure is implementation drift, test drift, spec ambiguity, or missing coverage.
Use specdd-debug to trace the active bootstrap chain, compare all relevant contract entries, fix the root cause, and report verification.
Best Practices
- Provide the failing behavior, target path, and relevant test command when available.
- Keep bootstrap and governing specs available before asking for code changes.
- Ask for a verification summary after the fix is complete.
Avoid
- Do not use this skill on projects without a SpecDD bootstrap.
- Do not ask the agent to change specs only to match broken behavior.
- Do not skip write authority checks before requesting edits.