triage

Convert raw scanner findings into categorized backlog work items.

Updated Apr 16, 2026

Search Tags:#workflow #prioritization #backlog #triage #cross-repo #findings

Ready to run

npx skills add https://github.com/opendatadiscovery/odd-team --skill triage-opendatadiscovery

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: triage
Source: https://github.com/opendatadiscovery/odd-team/tree/main/.claude/skills/triage
Command: npx skills add https://github.com/opendatadiscovery/odd-team --skill triage-opendatadiscovery

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert raw scanner findings into atomic backlog work items by prioritizing, categorizing, and tracking changes across repositories when triaging audit outputs.

Core Features & Use Cases

Backlog item creation: Transform each finding into a structured backlog entry (backlog/{category}/{ID}.md) with standardized fields.
Prioritization & categorization: Assign priority, category, and effort per finding, and flag dependencies or conflicts.
Cross-repo coordination: Identify findings that require coordination across multiple repos or upstream work.

Quick Start

Provide a findings file path to begin triage.

Frequently Asked Questions about triage

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

FAQPage Schema

How do I convert scanner findings into actionable backlog work items?▼

Triage scanner findings by providing a findings file path, which triggers automated backlog item creation that transforms each finding into a structured entry with standardized fields, priority assignment, category mapping, and cross-reference linking.

What is the best way to prioritize and categorize raw audit findings across multiple repositories?▼

You can prioritize and categorize audit findings across multiple repositories by assigning priority, category, and effort per finding while flagging dependencies or conflicts, and identifying findings that require cross-repo coordination or upstream work.

How do I track and coordinate upstream tasks from audit outputs in my workflow?▼

You can track and coordinate upstream tasks from audit outputs through cross-repo coordination, which identifies findings requiring multi-repo changes and converts them into categorized backlog items or upstream tasks with cross-reference linking to existing backlog entries.

Can I generate standardized backlog entries from a raw scanner findings file?▼

Yes, you can generate standardized backlog entries by providing a raw scanner findings file path, which triggers backlog item creation that transforms each finding into a structured entry at backlog/{category}/{ID}.md with standardized fields.

Does the triage process support cross-reference linking to existing backlog entries and issue drafts?▼

Yes, the triage process supports cross-reference linking to existing backlog entries and issue drafts, ensuring that newly created backlog items from scanner findings are properly connected to current tracking systems.

What limitations exist when triaging cross-repo findings that require upstream coordination?▼

When triaging cross-repo findings requiring upstream coordination, limitations apply to identifying findings that need coordination across multiple repositories, as the process focuses on converting findings into categorized backlog items rather than executing the upstream work itself.