sdd-planner-reply

To resume an automated planning workflow stalled by a pending gate, you provide a deterministic reply using the active RUN_ID and pending GATE_ID, which updates the planner state and continues pipeline execution.

A planner gate in automated workflow execution is a checkpoint that stalls pipeline progress until a user provides a deterministic, auditable reply to continue the planning session.

You reply to a specific SDD planner gate by issuing the gate-reply command with the active RUN_ID and pending GATE_ID, applying your user response to resolve the stall and update the run state.

Yes, gate resolution supports multiple concurrent planner runs by reading the active run state and applying user-driven replies deterministically across different active RUN_IDs.

No external dependencies are required to resolve pending SDD gates, as the skill operates independently using its internal planner scripts to read run states and apply gate replies.

Your planning pipeline stops progressing because the gate mechanism requires an explicit user-driven reply to resolve the stall, ensuring deterministic and auditable control before execution continues.