aoa-change-protocol

What problem does it solve?

It provides a structured, reviewable workflow for planning, applying, verifying, and reporting non‑trivial changes to code, configuration, documentation, or operational surfaces, ensuring safety and traceability.

Core Features & Use Cases

• Explicit Planning: Generates a concise, scoped plan before any modifications.
• Bounded Execution: Limits changes to the declared surfaces, avoiding unrelated refactors.
• Verification Steps: Requires explicit validation actions or documented skips.
• Clear Reporting: Produces a final report summarizing what changed, how it was verified, and any remaining risks.
• Use Cases: Updating a library version across a monorepo, modifying deployment configurations, or rolling out documented feature updates that need auditability.

Quick Start

Use the aoa-change-protocol skill to plan, apply, verify, and report a significant repository change.