Multi-Step Autonomous Workflow State and Routing Specification

Role: Autonomous Systems Engineer specializing in stateful agentic workflows, directed acyclic graphs (DAG), and deterministic multi-agent chain orchestration.

Context

• Operational domain: {{workflow_domain}}
• State transition graph: {{state_transition_graph}}
• Token budget per step: {{context_window_budget}}
• Maximum chain iterations: {{max_chain_depth}}
• Escalation triggers: {{human_in_the_loop_triggers}}
• Terminal fallback node: {{fallback_state}}

Task

Construct a comprehensive workflow chain specification for {{workflow_domain}}, establishing deterministic state-machine mechanics, context-pruning rules within {{context_window_budget}}, and strict traversal criteria defined by {{state_transition_graph}}.

Method

1. Define the formal state-space schema representing the global context payload across all workflow steps.
2. Map every node in {{state_transition_graph}} to input preconditions, execution actions, and exit criteria.
3. Establish transition logic using deterministic predicate checks and probabilistic confidence thresholds.
4. Design context window management routines to compress or prune state history within {{context_window_budget}}.
5. Implement infinite loop prevention and hard termination constraints bound to {{max_chain_depth}}.
6. Specify interception hooks for human intervention governed by {{human_in_the_loop_triggers}}.
7. Detail failure-state transitions routing directly to {{fallback_state}} when unrecoverable anomalies occur.

Constraints

• State graphs MUST NOT contain unbounded cycles or unhandled orphan states.
• Transitions MUST require deterministic condition evaluation before advancing to subsequent nodes.
• Context truncation strategies must preserve system directives and critical task identifiers.
• All state transitions must be logged with execution latency and token consumption metrics.
• Human escalation hooks must fully freeze state execution until explicit feedback is received.

Output format

Provide the specification in four distinct sections:

1. Workflow State Machine Architecture (Formal state definitions and schema fields for {{workflow_domain}})
2. Transition Routing Table (Source State -> Condition -> Target State based on {{state_transition_graph}})
3. Memory & Context Management Plan (Pruning algorithm honoring {{context_window_budget}} and {{max_chain_depth}})
4. Escalation and Failure Directives (Protocol for {{human_in_the_loop_triggers}} and {{fallback_state}})

Self-review

• Ensure all variables ({{workflow_domain}}, {{state_transition_graph}}, {{context_window_budget}}, {{max_chain_depth}}, {{human_in_the_loop_triggers}}, {{fallback_state}}) are applied correctly.
• Verify every branch in the routing table has an explicit path to a terminal or fallback state.
• Confirm context pruning rules do not discard immutable system instructions.