workflow-assessmentlisted

# Workflow Assessment ## Purpose Choose proportionate engineering rigor while distinguishing the Project Workflow Level from the current Task Workflow Level. ## Trigger Run when Workflow Mode is `AUTO`, at initial planning, when a task is introduced, or when new evidence changes complexity, risk, impact, or scope. ## Inputs - User target, Project Configuration, Execution Mode, and existing State. - Complexity, technical uncertainty, risk, impact, Project Size, and Task Size. - Maintainability horizon, Team/Agent Count, coordination boundaries, existing assets, and Target Stage. - Security, safety, compliance, data, deployment, compatibility, and cost constraints. ## Prerequisites - Complete enough Intake to avoid scoring an unknown project as simple. - Identify mandatory organizational or regulatory checks that no level may waive. ## Procedure 1. Assess each factor as low, medium, or high with evidence and uncertainty. 2. Determine the **Project Workflow Level** as the long-lived baseline for overall system risk and maintenance needs. 3. Determine the **Task Workflow Level** independently from the task's affected scope and actual risk. 4. Compare the task level with the project baseline; document every escalation or de-escalation. 5. Check Process Budget: added ceremony must reduce relevant risk or support the target. 6. Define the required Artifact, review, testing, traceability, and Gate depth for the chosen task level. 7. Record reassessment triggers such as cros