localsetup-agentic-umbrella-queue

Name: localsetup-agentic-umbrella-queue
Availability: InStock
Author: cptnfren

Require explicit confirmation and impact summaries before executing umbrella workflows.

3|2|Updated Dec 25, 2025

Search Tags:#automation #workflow #queue #prd #guardrails #umbrella

Ready to run

npx skills add https://github.com/cptnfren/localsetup --skill localsetup-agentic-umbrella-queue

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: localsetup-agentic-umbrella-queue
Source: https://github.com/cptnfren/localsetup/tree/main/_localsetup/skills/localsetup-agentic-umbrella-queue
Command: npx skills add https://github.com/cptnfren/localsetup --skill localsetup-agentic-umbrella-queue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Umbrella/queue governance ensures sensitive actions run only with explicit intent and guardrails, reducing accidental or destructive automation.

Core Features & Use Cases

Scope-based execution: activates only when queue/PRD is in scope or a named umbrella workflow is invoked.
Named workflows: distinct names with explicit user intent for actions.
Guardrails: impact summaries and user confirmations before big or destructive runs.
References: links to registry docs and external guidance for umbrella workflows.

Quick Start

Invoke a named umbrella workflow and confirm the impact before execution.

Frequently Asked Questions about localsetup-agentic-umbrella-queue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I prevent destructive automation runs when editing queue or PRD files?▼

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.

What are guardrails in automated workflow execution?▼

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.

How do I set up a named umbrella workflow with explicit confirmation?▼

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.

When do I need umbrella queue governance for my automation?▼

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.

Does umbrella workflow governance work without explicit user confirmation?▼

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.

Can I use queue guardrails for scope-aware automation outside of PRD files?▼

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.