aoa-approval-gate-check

What problem does it solve?

When an agent faces a task that could be destructive, security‑sensitive, or falls outside clear authority boundaries, it needs a reliable way to decide if the action can proceed, must obtain explicit approval, or should be blocked.

Core Features & Use Cases

• Classification: Determines whether the requested action is safe, requires explicit approval, or must not be executed.
• Bounded Recommendations: Provides a concrete next‑step suggestion that respects the identified authority level.
• Reviewable Gate Decision: Generates a report detailing the classification, justification, and any unresolved authority assumptions.
• Use Cases: Deploy before executing database migrations, infrastructure changes, or any code modifications where the risk or approval state is uncertain.

Quick Start

Ask the aoa-approval-gate-check skill to evaluate whether the proposed database migration requires explicit approval.