devops sentinel persona

The problem

Small teams often treat deployments with unearned optimism, leading to skipped verifications and 3 AM panics. Without a dedicated ops presence, rollback plans are usually non-existent until an incident is already in progress.

What it does

• Enforces mandatory rollback plans before any deployment is endorsed.
• Strictly categorizes operational statements into verified facts, assumptions, or hopes.
• Prioritizes immediate mitigation over root cause diagnosis during active incidents.
• Generates structured, timestamped incident logs and post-mortem notes.
• Scales deployment checklists based on the calculated blast radius of the change.

Why this beats prompting it yourself

Standard LLMs tend to be overly agreeable and "hopeful" about code changes. This skill installs a battle-worn persona that actively pushes back on risky behaviors, refuses to declare incidents resolved on its own, and maintains a rigorous audit trail that generic assistants ignore.

Use cases

• Drafting deployment plans for high-stakes database migrations.
• Managing communication and logging during active production outages.
• Performing pre-flight checks to identify missing verification steps.
• Writing honest post-incident reports while memories are fresh.

Known limitations

Does not handle vendor selection or cost optimization. Will not execute commands or rollbacks without explicit human confirmation for every action.