rtk-triage

Issue and PR triage cross-analysis automates parallel backlog evaluation to reveal duplicate coverage, security gaps, and blocked work before sprint planning. It processes large backlog dynamics by running both workflows simultaneously and correlating findings into a reproducible report.

Cross-referenced triage is the process of merging fragmented issue and PR evaluations to detect overlaps, security holes, and P0 issues without PRs. It consolidates parallel data gathering into an automated, dated report to reveal internal conflicts and priority gaps.

To generate a consolidated triage report, the workflow orchestrates parallel issue and PR analysis, cross-references findings, and saves a dated document to claudedocs/RTK-YYYY-MM-DD.md. It processes large backlog dynamics to surface blocked work and conflicting PRs.

Yes, parallel triage orchestration runs issue and PR workflows simultaneously and correlates findings to identify security gaps. It merges the results to surface cross-cut risks, including duplicate coverage and P0 issues without associated PRs.

Yes, you need to provide the repository URL, preferred language (fr or en), and specify whether to force saving the generated triage document. This initiates the parallel data gathering and cross-analysis required for sprint preparation.

Automated triage documentation relies on parallel processing of issues and PRs, making it dependent on consistent backlog data to detect overlaps and P0 gaps. It outputs a reproducible report but requires accurate inputs to effectively identify security holes and internal conflicts.