AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Speckit Debug

skill-wedabro-bro-skills-speckit-debug · by wedabro

Systematic Debugger - Diagnose problems, find individual root causes, and recommend fix plans.

↗ Repository
— No reviews yet
0 installs
38 views
0.0% view→install

Install

$ agentstack add skill-wedabro-bro-skills-speckit-debug

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-wedabro-bro-skills-speckit-debug)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● 2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Speckit Debug? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

🎯 Mission

Use scientific methodology to find the root cause of bugs without disturbing the main context of feature development.

📋 Protocol

Phase 1: Symptom Gathering (Symptom collection)

Before starting to code, make it clear:

  • Expected behavior: What is the expected result?
  • Actual behavior: What is the actual result that is happening?
  • Error messages: Specific error logs (paste directly).
  • Reproduction: Specific steps to reproduce the error (required).

Phase 2: Isolation & Hypothesis (Isolation & Hypothesis)

  • Create file .agent/debug/[issue-slug].md to save the investigation log.
  • Hypotheses: "Maybe the error lies in function X because of Y".
  • Use the commands grep , log to verify the hypothesis.

Phase 3: Root Cause Found (Determine the cause)

  • Only end the investigation when the specific line of code/configuration causing the error is found.
  • Explain WHY it fails instead of just saying IT IS ERROR.

Phase 4: Fix Proposal (Proposal to fix errors)

  • Do not correct errors directly in this skill.
  • The output is either a proposed fix or the creation of a gap_plan for speckit.implement to execute.

🚫 Guard Rails

  • NO guessing. Every conclusion must have evidence from logs or code.
  • DO NOT further damage existing code during debugging (use Read-only tools mainly).
  • MUST create a debug log file to save traces.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Write a review

Versions

  • v0.1.0 Imported from the upstream source.

More in Developer Tools