status-progression

To determine the next status, the Skill delegates to the get_next_status tool, reading the current state and tags against your configured flows in .taskorchestrator/config.yaml to recommend the appropriate forward, backward, or emergency transition.

A StatusValidator error blocks transitions when current task conditions fail to meet the required rules. This Skill interprets these validator messages and explains exactly what your config.yaml requires to successfully unlock the progression.

The best way to explain custom status progression is using this Skill to load and translate the status_progression and status_validation sections of your config.yaml into clear, actionable guidance for allowed transitions and emergency patterns.

No, you cannot use this Skill to enforce transitions automatically. It acts as a lightweight coordinator that explains outcomes and clarifies options based on your config, deliberately ensuring configuration-driven orchestration without performing the actual validation.

You need to use an emergency status when your workflow encounters exceptional conditions that bypass standard sequential paths. This Skill reads your config.yaml to describe exactly when these emergency transition patterns are permitted.

No, status-progression does not work without the config.yaml file. It relies entirely on reading the status_progression and status_validation rules defined within your .taskorchestrator configuration to generate accurate workflow guidance.