approval

Present a plan and halt execution until explicit user approval.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/fredericpoitevin/.cursor --skill approval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: approval
Source: https://github.com/fredericpoitevin/.cursor/tree/main/skills/approval
Command: npx skills add https://github.com/fredericpoitevin/.cursor --skill approval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Before making any changes, present your plan first and wait for explicit approval. Do not execute or implement anything until I confirm.

Core Features & Use Cases

  • Approval gate: forces explicit authorization before actions that modify systems or data.
  • Plan presentation: generates a clear, actionable plan detailing intended changes.
  • Safety guardrails: prevents execution until explicit confirmation is provided by the user.

Quick Start

Present your proposed plan and wait for explicit approval before acting.

Frequently Asked Questions about approval

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

FAQPage Schema
How do I require explicit approval before executing workflow actions?

An approval gate enforces explicit authorization by presenting a detailed plan and halting execution until human verification confirms the intended system or data changes.

What is an approval gate in workflow governance?

An approval gate is a safety guardrail in workflow governance that prevents unintended actions by requiring explicit human confirmation before proceeding with any execution that modifies systems or data.

How do I add safety guardrails to prevent unintended system modifications?

You add safety guardrails by enforcing an explicit confirmation step that generates a clear plan of intended changes and stops execution until the user provides explicit approval.

Can I present a plan and wait for confirmation before modifying data?

Yes, you can present a detailed execution plan and wait for explicit confirmation before modifying data, ensuring all intended changes undergo human verification prior to any action.

When do I need an approval gate for task execution?

You need an approval gate for task execution whenever actions could modify systems or data, requiring human verification to prevent unintended changes during workflow planning and governance.

Does this approval workflow require any dependencies or components?

No, this approval workflow requires no dependencies or components, functioning as a basic governance guardrail that solely enforces explicit authorization before execution proceeds.