Results for “production-incidents”

Incident response mode — diagnose a production issue, write a postmortem, add follow-up tasks to TODO.md. Use when user says "/incident [description]".

Captures operational workflows, release procedures, incident patterns, or support processes as repeatable runbooks.

OI-3 spike harness — heavy consumer skill, BASELINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow by reading a file directly, with NO Skill-tool call. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

OI-3 spike harness — heavy consumer skill, INLINE arm. Builds an incident post-mortem and sources the readability standard mid-workflow via an inline (non-forked) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

OI-3 spike harness — heavy consumer skill, FORKED arm. Builds an incident post-mortem and sources the readability standard mid-workflow via a forked (context fork) guidance skill. Use only when explicitly invoked by the spike harness with a TRIAL_ID and data path.

Generates ad copy, email sequences, long-form articles, and product descriptions with structured briefs and templates for content production.

Content Factory video production loop for Cursor agents. Use when the user says @video-loop, make/create/generate a video with Content Factory, or asks to run a calendar slot into a finished accepted video. Enforces plan APPROVE gate and video-acceptance criteria before completion.