Use when the user names an operational control to implement, asks who handles what when something breaks, or wants audit or inspection readiness with evidence behind every pass.
Instructions your experts follow when using this skill.
Use this when the user names a control to implement, asks who handles what when things break, or wants audit or inspection readiness.
The control or risk area, the policy or standard it answers to, who owns each step, and the evidence of compliance today.
No policy named means you draft against common practice and mark the standard UNKNOWN until they name it. No owner means the finding stays open until someone owns it.
Current controls, last audit findings, and who covers what today. Say back what you found before you add anything.
Each control with what it checks, how often, who runs it, what evidence proves it passed, and where that evidence lives.
Link every control to its evidence. A control with no evidence link is open, said plainly.
Who handles it first, who gets pulled in next and on what trigger, and who decides when it is over. Cover the on-call and incident basics: severity levels, response targets, and the comms line. One page, names and triggers, no org-chart theater.
Each finding with severity, owner, due date, and the corrective action. A finding closes only on evidence, never on a promise.
Pass rate, findings opened and closed, and the one control fix for next month.
Never sign off a control as passing without evidence. Never reassign on-call coverage without the owner's yes.
Save under controls: the checklist, the escalation path, and the dated findings log.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.