hitl-approval

Present plans for explicit user approval before proceeding.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/metasaver/claude-marketplace --skill hitl-approval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hitl-approval
Source: https://github.com/metasaver/claude-marketplace/tree/main/plugins/metasaver-core/skills/workflow-steps/hitl-approval
Command: npx skills add https://github.com/metasaver/claude-marketplace --skill hitl-approval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a generic approval gate to obtain explicit user consent before proceeding with major workflow steps.

Core Features & Use Cases

  • Auto-approval rules: Fast-path for simple tasks.
  • Human approval: Presents a clear summary with options for approval or revision.
  • Structured output: Returns approved decisions and optional feedback.

Quick Start

Trigger HITL approval when a plan requires explicit human validation; respond with approval or revisions.

Frequently Asked Questions about hitl-approval

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

FAQPage Schema
How do I add an approval gate to my workflow before executing plans?

An approval gate presents your plan or summary to users and requests explicit confirmation before proceeding. It's applied after analysis steps like audit, build, or debug to validate directions, then returns approved status and optional feedback for next steps.

Can I skip approval for simple tasks automatically?

Yes, the approval gate auto-approves low-complexity tasks (complexity < 15) when fast-path is enabled or when prompts contain 'do without approval' or 'just do it', streamlining workflows for straightforward work.

What does the approval gate return after a user decision?

The approval gate returns a structured object containing an approved field (true/false) and optional feedback field, enabling downstream steps to branch on user consent and capture revision notes.

When should I use a workflow approval gate instead of proceeding directly?

Use an approval gate when validating remediation plans, technical directions, or implementation approaches after analysis—any major workflow step where explicit user consent reduces risk before execution.

Does the approval gate work with existing analysis Skills like audit and build?

Yes, the approval gate integrates as a generic gate applied after analysis Skills such as audit, build, architect, or debug to validate their outputs before proceeding with implementation.