Results for “production-incidents”

Generates video analysis reports by routing to a VLM backend for per-clip analysis or an analytics backend for incident-range reports, with deployment profile verification and URL rewriting.

Video production specialist for short-form, long-form, episodic, and motion graphics video. Trigger when user requests 'create video', 'make reel', 'tiktok video', 'youtube video', 'add subtitles', 'generate voiceover', 'clip video', or 'motion graphics'.

Structured producer who turns research insights into production-ready slide deck outlines and scripts. Triggers: 'create slides', 'write webinar script', 'build slide deck', 'webinar outline', 'produce webinar', or when user asks for the Producer.

Turn a "when X happens, do Y" idea into a precise build prompt for an automation platform (n8n, Make, Zapier, and others). Trigger on "build an automation", "n8n prompt", "Make scenario", "Zapier prompt", "automate this workflow", "when X happens do Y", or any request to wire up a no-code or low-code workflow.

Composite skill — runs the postmortem chain after any production incident (`/hotfix`, rollback, or prod outage acknowledged). Chains adt-research (root-cause learning) → adr-write (decision capture) → generate-tests (regression test) → security-sweep (conditional, only if root cause is auth/input/secret-related) → knowledge-loop (memory + RAG curation) → handoff. Stops the silent-postmortem failure mode where a hotfix ships and the lessons evaporate. Auto-queues after `/hotfix` Phase 10 completes; also fires when user says "postmortem", "what did we learn", "write up the incident".

Use for writing, reviewing, debugging, testing, or analyzing Python SimPy discrete-event simulations. Trigger on Environment, Event, Process, timeout, Resource, PriorityResource, PreemptiveResource, Container, Store, queues, interrupts, simulation clocks, replications, or SimPy monitoring. Do not use for asyncio services, wall-clock schedulers, continuous ODE solvers, or Monte Carlo code without an event-process model.

Systematic debugging workflow for errors and bugs. Use when debugging errors, investigating bugs, troubleshooting issues, or when something isn't working as expected. Integrates Sentry MCP for production error context, Firecrawl for researching fix patterns, and Sequential Thinking for complex multi-step diagnosis.