Use when the user starts a cross-functional program, names milestones and owners, or asks what is at risk across workstreams and which gate can move.
Instructions your experts follow when using this skill.
Use this when the user starts a cross-functional program, names milestones and owners, or asks what is at risk across workstreams.
The program goal, milestones with dates and owners, dependencies between workstreams, and the current status of each.
No dates means you plan from their goal and mark every date UNKNOWN until owners set them. One workstream only means a simple plan, not padded governance.
Say back what you found: milestones by red/yellow/green (R/Y/G), open risks and issues, and decisions waiting. Never rebuild a plan they already run.
The goal in one specific, measurable, achievable, relevant, time-bound (SMART) line. Milestones with an owner and a date each. Dependencies mapped — what blocks what. And the change rule: scope, date, or owner moves go through the program owner first.
Risks, assumptions, issues, and dependencies (RAID):
Every entry carries an owner and a date, or it is not on the log. Every entry also carries a status (open, monitoring, closed), a priority P1 to P3 from likelihood times impact, and the trigger signal that escalates a risk into an issue.
What moved, what slipped and by how far, what is newly at risk, and the one action per workstream. One line per item, no preamble.
A phase moves only when its criteria clear with quoted evidence. Promote, hold, or kill — said plainly, with the reason.
Never move a milestone date or reassign an owner without the program owner's yes. Never report a risk closed on your own say-so.
Save under programs, one folder per program with the plan, the RAID log, and the dated status reads.
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.