|
| 1 | +--- |
| 2 | +name: agent-ops-mini-sprint |
| 3 | +description: 'Evidence-first operating workflow for production incident triage, PR risk review, deploy smoke checks, and handoff notes from public or sanitized context.' |
| 4 | +--- |
| 5 | + |
| 6 | +# Agent Ops Mini-Sprint |
| 7 | + |
| 8 | +Use this skill when a user needs a small, bounded operations sprint with AI coding agents: |
| 9 | + |
| 10 | +- production bug or incident triage |
| 11 | +- PR risk review |
| 12 | +- deploy smoke checks |
| 13 | +- AI-generated code cleanup scoping |
| 14 | +- implementation handoff from public or sanitized evidence |
| 15 | + |
| 16 | +## Operating Rules |
| 17 | + |
| 18 | +- Work from evidence before naming a cause. |
| 19 | +- Separate observed facts, assumptions, and unknowns. |
| 20 | +- Use absolute timestamps when investigating incidents or deploy windows. |
| 21 | +- Split the path by layer: frontend, API, auth, database, queue/cache, worker/webhook, provider, runtime, and deploy. |
| 22 | +- Prefer read-only checks before mutations, restarts, rollbacks, or manual data edits. |
| 23 | +- Never request or expose secrets, tokens, private customer data, payment details, or credentials. |
| 24 | +- Keep the first deliverable small enough to verify in one review cycle. |
| 25 | + |
| 26 | +## Incident Triage Output |
| 27 | + |
| 28 | +Return: |
| 29 | + |
| 30 | +1. current read: what is happening, what is not proven, whether it is ongoing |
| 31 | +2. timeline: report time, deploys, logs, alerts, admin actions, provider events |
| 32 | +3. layer checks: fastest read-only proof for each plausible layer |
| 33 | +4. likely causes: ranked by evidence strength with why each may be wrong |
| 34 | +5. safe next action: smallest check or patch that increases certainty or reduces impact |
| 35 | + |
| 36 | +## PR Risk Review Output |
| 37 | + |
| 38 | +Lead with findings, not summary. |
| 39 | + |
| 40 | +For each finding include: |
| 41 | + |
| 42 | +- severity |
| 43 | +- file or route evidence |
| 44 | +- failure mode |
| 45 | +- missing test or verification |
| 46 | +- minimal fix direction |
| 47 | + |
| 48 | +Prioritize correctness, security, data loss, auth, money-path behavior, race conditions, and deploy regressions over style. |
| 49 | + |
| 50 | +## Deploy Smoke Output |
| 51 | + |
| 52 | +Return: |
| 53 | + |
| 54 | +- target environment and deploy identifier |
| 55 | +- health endpoints or user flows checked |
| 56 | +- runtime/log checks |
| 57 | +- rollback watchpoints |
| 58 | +- before/after evidence |
| 59 | +- handoff note for the next operator |
| 60 | + |
| 61 | +## Paid Sprint Intake |
| 62 | + |
| 63 | +If the user wants a human-reviewed mini-sprint, ask them to open a sanitized request: |
| 64 | + |
| 65 | +https://mysubb01.github.io/agent-ops-command-pack-teaser/order.html |
| 66 | + |
| 67 | +Public issues are only for sanitized context, scope, budget, and acceptance criteria. Payment links, invoices, and private handoffs happen outside public issues. |
0 commit comments