Sort contract deviations by the user's playbook priority and route each one to its business owner or counsel.
Instructions your experts follow when using this skill.
Use a completed playbook comparison. Triage is queue order, not legal risk advice.
If the user's playbook names escalation classes, thresholds, owners, or fallbacks, apply them and cite the rule. If it does not, use neutral process labels:
COUNSEL DECISION — a legal position or unsupplied fallback is needed;BUSINESS INPUT — price, scope, service, timing, or owner fact is missing;PLAYBOOK MATCH — the supplied position matches;DOCUMENT GAP — text, definition, exhibit, or version is missing;READY FOR CONFIRMATION — all requested evidence is present, but no approval is implied.Never create high, medium, or low legal-risk grades unless the supplied playbook defines them. Never infer authority from a job title.
Return one row per issue with source section, playbook rule, label, owner, deadline, blocker, supplied fallback, and exact decision. Keep all approvals pending until the named owner records them. Do not accept text, negotiate, or send changes.
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.