gov-plan-gate

Require explicit user confirmation before executing deployment or merge actions.

5|Updated Feb 16, 2026
One-click install
npx skills add https://github.com/technomensch/knowledge-graph --skill gov-plan-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gov-plan-gate
Source: https://github.com/technomensch/knowledge-graph/tree/main/skills/gov-plan-gate
Command: npx skills add https://github.com/technomensch/knowledge-graph --skill gov-plan-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enforces strict user confirmation workflows, preventing accidental or unauthorized actions during planning and deployment stages.

Core Features & Use Cases

  • Approval Gates: Requires explicit "Proceed" or "Start" commands before executing deployment steps or pushing code.
  • Behavior Control: Halts processes until user confirmation, ensuring responsible task progression.
  • Use Case: A team deploying code can verify each step, reducing mistakes by requiring user approval before pushing changes or merging pull requests.

Quick Start

When ready to push code, the Skill asks for confirmation by awaiting a "Proceed" command before executing the push.

Frequently Asked Questions about gov-plan-gate

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

FAQPage Schema
How do I require explicit user approval before pushing code or merging a PR?

To require explicit user approval before a code push or PR merge, you need an approval gate that halts the workflow until a confirmation command like "Proceed" is received. This prevents accidental deployments by blocking direct actions.

What are workflow approval gates and how do they prevent accidental deployments?

Workflow approval gates are checkpoints that pause development processes during planning and execution stages. They prevent accidental deployments by blocking direct push or PR actions until the user explicitly confirms they want to proceed.

How do I add a confirmation step to my development workflow for team deployments?

You can add a confirmation step to your development workflow by implementing an approval gate that halts processes before execution. This ensures responsible task progression by requiring team members to explicitly verify each deployment step.

Can I halt a deployment process until a specific confirmation command is provided?

Yes, you can halt a deployment process until a specific confirmation command is provided. The workflow blocks direct actions and waits for explicit commands like "Proceed" or "Start" before executing the push or merge steps.

Do I need any specific dependencies to set up manual PR approval workflows?

No specific dependencies are required to set up manual PR approval workflows. You can implement user confirmation gates directly within your existing planning and deployment stages without external tools or modules.