issue-processor

Issue triage into a product-definition pipeline involves classifying incoming bugs, signals, and feature requests into categorized items. This process enriches entries with contextual links to FRDs and ADRs, then routes them to work orders or questions for coordinated planning.

The best way to categorize product issues is to apply hub-defined categories from product.md, automatically associating each issue with relevant decisions and ADRs. This ensures issues feed directly back into the product-definition workflow with full context.

Yes, you can deduplicate market signals and observations during processing. The system prevents duplicates and surfaces patterns for consolidation before routing enriched items to work order workflows or QA questions.

Issue classification handles environment details and recent changes by enriching each categorized item with contextual references. It links related files, recent modifications, and environment specifics directly to the triaged entry for better decision-making.

Yes, this issue processing approach works for managing tensions and risks alongside standard bugs. It transforms diverse inputs—including framework changes and questions—into structured items that feed the product-definition pipeline uniformly.