localsetup-agentic-umbrella-queue

Umbrella workflow governance prevents destructive automation by enforcing scope-aware execution on queue and PRD file edits. It requires explicit user intent, an impact summary, and confirmation before executing complex workflows, ensuring sensitive actions run safely.

Guardrails in automated workflow execution are safety mechanisms that generate impact summaries and require explicit user confirmation before running big or destructive tasks. They ensure umbrella workflows only execute with verified, explicit intent to prevent unintended damage.

Setting up a named umbrella workflow requires invoking a distinct workflow name to declare explicit user intent. The governance system then imposes guardrails, presenting an impact summary that you must approve before the automation executes.

You need umbrella queue governance when your automation edits files in .agent/queue/**, .agent/**, PRD.md, or *.prd.md. It activates automatically in these scopes or when a named umbrella workflow is invoked to ensure safe execution.

No, umbrella workflow governance does not execute big or complex workflows without explicit user confirmation. It deliberately imposes guardrails and requires an impact summary to be approved, ensuring sensitive actions never run automatically without intent.

Yes, you can use queue guardrails for scope-aware automation outside of PRD files. The governance activates for edits in .agent/queue/** and .agent/** directories, or whenever a named umbrella workflow is explicitly invoked.