sus-resolution

To automate Jira issue routing for SUS maintenance tasks, the orchestrator fetches issue data via Jira MCP, applies product mapping heuristics, and delegates work to the correct domain skill based on confidence scoring.

The best way to orchestrate resolution across multiple SUS task scenarios is to use an orchestrator that evaluates product context, scores confidence, and routes work to specialized domain skills like resolve-analytics or resolve-fvc.

To track time and finalize Jira issues after completing a SUS fix, you invoke a finalization step that registers progress in Jira and loads learned patterns for future task resolution.

Yes, you can use this orchestration workflow for .NET integration and analytics tasks, as it evaluates product context and routes work to domain skills specialized in those specific areas.

Confidence scoring when delegating SUS tasks evaluates product context and applies learned heuristics to determine the most appropriate domain skill for routing the specific issue.