skills.rest
Hoang604
Hoang604COMMUNITY
Explore all skills by this author →
GitHub

d-symptom

Clarifies bug symptoms into reproducible SYMPTOM.md reports via guided elicitation.

Updated Jan 22, 2026
Search Tags:#workflow#debugging#documentation#reproduction#clarify#symptom
One-click install
npx skills add https://github.com/Hoang604/get-thing-done --skill d-symptom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: d-symptom
Source: https://github.com/Hoang604/get-thing-done/tree/main/.claude/skills/d-symptom
Command: npx skills add https://github.com/Hoang604/get-thing-done --skill d-symptom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Clarifies bug symptoms into precise, reproducible reports. This workflow ensures teams can quickly understand issues without ambiguity.

Core Features & Use Cases

  • Guided symptom elicitation prompts users with targeted questions to define expected vs actual behavior.
  • Document-ready symptoms: generates the SYMPTOM.md file under the path ./.gtd/debug/current.
  • Reproducible steps & environment capture: records steps, conditions, and context to enable reliable reproduction.

Quick Start

Describe the symptom you observe and let the assistant guide you through clarifying questions to produce SYMPTOM.md.

Frequently Asked Questions about d-symptom

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document a bug symptom into a reproducible report?▼

You clarify a bug symptom by describing the observed issue to an interactive workflow that asks targeted questions and generates a structured SYMPTOM.md file capturing expected vs actual behavior, reproduction steps, conditions, and environment.

What is a symptom report and when do I need one for debugging?▼

A symptom report is a precise documentation of a bug's expected vs actual behavior, reproduction steps, conditions, and environment. You need one during debugging to ensure teams can quickly understand and reliably reproduce issues without ambiguity.

How do I create a SYMPTOM.md file for my debugging workflow?▼

You create a SYMPTOM.md file by entering your observed symptom into an interactive elicitation workflow, which mirrors your understanding and outputs the documented file automatically into the ./.gtd/debug/current directory.

Does interactive symptom elicitation work without prior debugging setup?▼

Yes, interactive symptom elicitation requires minimal inputs and operates safely with user confirmation. It needs no prior dependencies, guiding you through the symptom clarification process from scratch.

What sections are included in a structured bug reproduction document?▼

A structured bug reproduction document includes sections for Expected behavior, Actual behavior, Reproduction steps, Conditions, and Environment. These sections ensure consistent documentation for reliable issue reproduction.

Related Skills

Explore More Software Engineering Skills→
simonwjacksonsimonwjackson

se-debug

Trace causal chains from trigger to symptom to confirm root causes.

Community
Advanced
Hoang604Hoang604

d-archive

Archive completed debug investigations from .gtd/debug/current/ into timestamped folders under .gtd/archive.

Community
Intermediate
nanorepublicananorepublica
61

Global Tech Stack

Validate code against centralized global tech stack standards.

Community
Basic
baphledbaphled
1

create-bug

Structure bug reports with reproduction steps, severity, and environment details.

Community
Intermediate