operator-triage

Triage operator documents by evaluating content and applying a decision framework that routes items to Investigation, Proposal, Plan, Development, Lesson Learned, or Fragment stages. It assesses bugs, fragments, on-deck, and proposals to enable consistent routing decisions.

Batch triage multiple operator items by reading and assessing each document, then mapping outcomes to workflow stages and creating actionable tasks. This enables coordinated follow-ups by recording clear next steps for every routed item.

The triage workflow maps documents by evaluating their content against a documented framework, routing each item to Investigation, Proposal, Plan, Development, Lesson Learned, or Fragment based on assessment outcomes and folder location.

Authentication is required to access and triage operator folders. You must authenticate with Operator, locate items to triage across bugs, fragments, on-deck, proposals, and archives, then route each document to its appropriate workflow stage.

A structured triage workflow reduces ambiguity and manual effort by guiding teams to consistently review operator documents and decide next steps. It follows a documented mapping to ensure routing decisions align with pipeline stages and create actionable tasks.

Automated task creation records triage outcomes as actionable tasks with clear next steps. After assessing operator documents like proposals and fragments, the workflow creates tasks mapped to the appropriate development stage for follow-up.