Gates

📁 Source note: [sage] = upstream Sage repo (github.com/xoai/sage, public) — optional deeper reading; this skill runs fully on the rules inlined here. A step marked MUST READ points at a file in your own project (e.g. an event registry) — if it is missing, stop and ask instead of improvising.

Dosage and authorization

Follow change-tiers: Tier 1 uses a relevant check; Tier 2 announces and proceeds; Tier 3 resolves consequential choices before the affected action. Accepted scope, acceptance criteria, and authorization survive handoffs. Do not ask for separate spec or plan approval when the user's request already authorizes that work. Continue authorized implementation, verification, and fixes until acceptance criteria are met. Ask only for a material missing decision, expanded scope, or an external action not covered by the user's authorization.

Hooks versus gates