mysql-operations

# MySQL Operations Acknowledgement: Shared by Peter Bamuhigire, techguypeter.com, +256 784 464178. Use this parent skill as the active MySQL operations entrypoint. Operational advice must be tied to observable evidence and a reversible execution path. <!-- dual-compat-start --> ## Use When - Troubleshooting slow queries, lock waits, replication lag, connection exhaustion, deadlocks, or storage pressure. - Designing backup, restore, HA, monitoring, capacity, and maintenance plans for MySQL. - Reviewing production configuration, operational runbooks, and incident evidence. ## Do Not Use When - The task is unrelated to this parent skill or is better handled by a narrower active parent named in the workflow. - The request only needs a trivial answer and no reference module needs to be loaded. ## Required Inputs - Gather the concrete system, repository, environment, constraints, and deliverable before loading references. - Identify which absorbed reference file is needed; do not load every migrated reference by default. ## Workflow 1. Load `database-reliability` for SLOs, recovery objectives, and incident handling. 2. Load the task-specific reference: - `references/mysql-administration.md` for roles, backup, restore, replication, upgrades, and maintenance. - `references/mysql-query-performance.md` for query tuning, indexes, EXPLAIN review, and capacity analysis. 3. Pair with `mysql-engineering` when schema or SQL changes are part of the work. 4. Pair with `observabil...