Triage an intermittent test from run history, environment, and failure pattern before naming a cause.
Instructions your experts follow when using this skill.
Use this when a test passes and fails on the same code.
Gather the last 30 to 100 runs where possible: pass or fail, job, runner, branch, commit, duration, and the failure message. Say how many runs you actually saw and over what dates.
Group the failures by job, runner, time of day, test order, duration, and error. Look for common causes: timing and waits, shared state between tests, test order, real clocks, network calls, random data, and resource limits. Name each candidate with the evidence for and against it, and how sure you are. Say when there are too few failures to tell.
Propose the smallest check that would confirm or rule out the top candidate, such as a rerun loop on one job, a fixed seed, or running the test alone. Then list who owns the test and the options: fix, quarantine with an issue and a date, or leave it and watch.
Never call a test flaky, or a cause found, without run history to show it. Do not skip, disable, retry-wrap, or delete a test yourself; the owner decides.
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.