skills.rest
jupes
jupesCOMMUNITY
Explore all skills by this author →
GitHub

triage-issue

Investigate reported bugs and create Beads issues with TDD fix plans.

2|Updated Apr 11, 2026
Search Tags:#code quality#TDD#issue management#issue tracking#bug investigation
One-click install
npx skills add https://github.com/jupes/agent-forge-harness --skill triage-issue-jupes
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: triage-issue
Source: https://github.com/jupes/agent-forge-harness/tree/main/.claude/skills/triage-issue
Command: npx skills add https://github.com/jupes/agent-forge-harness --skill triage-issue-jupes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill simplifies the process of diagnosing bugs and creating issues with a behavior-level Test-Driven Development (TDD) plan.

Core Features & Use Cases

  • Bug Investigation: Investigate reported issues, diagnose root causes, and capture symptoms for further analysis.
  • Issue Creation: Create and manage Beads issues with a detailed TDD fix plan, prioritizing and updating as needed.
  • Use Case: When a user reports a bug, use this Skill to capture the issue, investigate, and create a Beads issue with a clear TDD plan for a fix.

Quick Start

To create an issue for a reported bug, use the triage-issue skill and follow the prompts to describe the problem and its symptoms.

Frequently Asked Questions about triage-issue

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

FAQPage Schema
How do I document a bug investigation with a TDD fix plan?▼

To document a bug investigation with a TDD fix plan, diagnose the reported issue's root cause and capture its symptoms to create a Beads issue featuring a detailed behavior-level testing strategy.

What is the best way to track reported bugs using behavior-level TDD?▼

Tracking reported bugs using behavior-level TDD involves investigating the symptoms, diagnosing the root cause, and filing a Beads issue with a structured Test-Driven Development plan to guide the fix.

Can I use this approach to coordinate issue tracking and bug diagnosis?▼

Yes, you can coordinate issue tracking and bug diagnosis by investigating the reported problem, capturing the symptoms for analysis, and creating a managed Beads issue with a prioritized TDD fix plan.

How do I create Beads issues with a Test-Driven Development fix plan?▼

You create Beads issues with a Test-Driven Development fix plan by inputting the reported bug's symptoms and diagnostic findings, which generates a prioritized issue with a clear behavior-level testing strategy.

Why include behavior-level testing in issue management and bug triage?▼

Including behavior-level testing in issue management ensures that bug triage produces a clear, structured TDD fix plan in the Beads issue, prioritizing expected behavior to guide the actual code correction.

Related Skills

Explore More Software Engineering Skills→
yocxy2yocxy2

gstack-openclaw-investigate

Trace software symptoms to architectural root causes via a five-phase diagnostic workflow.

Community
Advanced
drshailesh88drshailesh88

triage-issue

Diagnose bug root causes and create GitHub issues with TDD fix plans.

Community
Advanced
strawgatestrawgate

find-stale-issues

Identify stale, resolved, or duplicate GitHub issues via semantic similarity analysis.

Community
Advanced
RussianLioNRussianLioN
1

health-bugs

Detect, prioritize, and fix software bugs with type-checking and build quality gates.

Community
Advanced