standing-approval-and-auto-advance

What problem does it solve?

This Skill helps teams reduce repetitive approval friction in tightly governed delivery loops without accidentally widening autonomy into unsafe areas. It defines when mechanical steps can continue without re-asking permission, while preserving human control over protected actions and reviewer overrides.

Core Features & Use Cases

• Standing scope definition: Clearly names the loop steps, branches, and change classes covered by ongoing approval.
• Phase auto-advance: Allows progress only into already named and individually approved phases, stopping on scope drift.
• Governance safeguards: Requires a per-session restatement, an exact opt-out phrase, and a reviewer-block path that suspends the loop immediately.
• Use case: A team repeatedly approves the same push, PR, and CI-fix cycle and wants a durable policy that avoids rubber-stamping while still respecting human-only merge and deployment floors.

Quick Start

Ask the assistant to draft a governed standing-approval policy for your repo, including named scope, an exact opt-out phrase, phase-advance rules, and reviewer-block behavior.