triage

Convert external bug reports into PDDA-compliant remediation project documents.

2|Updated Jun 24, 2026

Search Tags:#documentation #workflow automation #github #triage #bug tracking #pdda

Ready to run

npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill triage-hypercart-dev-tools

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/Hypercart-Dev-Tools/pdda/tree/main/.claude/skills/triage
Command: npx skills add https://github.com/Hypercart-Dev-Tools/pdda --skill triage-hypercart-dev-tools

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve?

This skill solves the problem of unorganized, high-volume feedback and bug reports that often get lost or remain unactionable, ensuring every report is captured, validated, and tracked within a structured project lifecycle.

Core Features & Use Cases

Automated Intake: Fetches external bug reports or feedback and converts them into standardized, PDDA-compliant project documentation.
Checklist-Driven Planning: Automatically generates a multi-phase remediation plan, including dedicated discovery and reproduction steps.
Lifecycle Integration: Automatically links reports to GitHub issues and maintains a roadmap pointer to ensure visibility and accountability.

Quick Start

Use the triage skill to process the report at the provided URL and create a new remediation project document.

Frequently Asked Questions about triage

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

FAQPage Schema

How do I convert external bug reports into structured project documentation?▼

To convert external bug reports into structured project documentation, you can use automated triage workflows that fetch report content and transform it into standardized, PDDA-compliant remediation documents. This ensures high-volume feedback is captured and validated within a structured project lifecycle.

How do I automate GitHub issue creation from incoming feedback threads?▼

Automating GitHub issue creation from incoming feedback involves linking the triaged reports directly to GitHub issues. This lifecycle integration maintains a roadmap pointer to ensure visibility and accountability for every validated bug report throughout the remediation process.

Do I need the GitHub CLI to manage automated bug tracking and triage?▼

Yes, you need the GitHub CLI to manage automated bug tracking and triage. The process requires GitHub CLI authentication to manage issue tracking and establish the documentation lifecycle links necessary for PDDA-compliant remediation project documents.

What is a PDDA-compliant remediation project document?▼

A PDDA-compliant remediation project document is a structured format for tracking bug fixes that includes a multi-phase remediation plan with dedicated discovery and reproduction steps. It standardizes unorganized feedback into actionable project documentation.

Can I generate a multi-phase remediation plan directly from a bug report URL?▼

Yes, you can generate a multi-phase remediation plan directly from a bug report URL. The triage mechanism fetches the report content, performs light validation, and automatically establishes tracking via GitHub issues and roadmap pointers for the project.

What is the best way to handle high-volume feedback without losing track of bug reports?▼

The best way to handle high-volume feedback is to use an automated triage workflow that captures, validates, and tracks every bug report. This prevents reports from remaining unactionable by converting them into structured project documentation with GitHub issue tracking.