• You need a structured QA workflow for daily delivery rhythm.
• Multiple testing activities must be orchestrated, not run ad hoc.
• Team needs transparent status, dependency handling, and risk escalation.

• Build an execution sequence from analysis to verification to reporting.
• Deliver day-level risk control with traceable evidence.
• Expose daily blockers and regression drift early, with owner and due date.

1. Confirm objective, scope, entry criteria, and exit criteria.
2. Split work into phases: preparation, execution, consolidation, sign-off.
3. Assign owner, deadline, and dependency for each phase task.
4. Run critical-path tests first, then supporting and edge checks.
5. Summarize findings by severity, business impact, and fix readiness.
6. Publish workflow result: pass/fail status, residual risk, next action.

Input:

• Scope: payment + coupon + order split
• Time: 3 days
• Goal: release confidence

Output:

• Workflow board with owner and schedule
• Priority execution order and risk log
• Final decision note with blocking and non-blocking issues

Input:

• "Please test core flows before launch"

Output (problem):

• No phase split, no owners, no completion criteria
• Team cannot judge progress or release readiness

• Do not run workflow without explicit entry/exit criteria.
• Do not hide blockers in summary-level status updates.
• Do not skip evidence collection for key decisions.
• Do not convert workflow into a static checklist without reprioritization.
• Do not output go/no-go recommendation when critical data is missing.