Turn a hiring need into a plain job description based on outcomes, job-related evidence, and approved terms.
Instructions your experts follow when using this skill.
Use this before publishing or revising a role.
Get the reason for the hire, outcomes due in the first 30, 60, and 90 days, recurring work, decisions the role owns, manager, team, location, working hours, travel, approved level, approved pay range, and required legal text. For each requirement, ask what work would fail without it.
Sort requirements into:
Remove the last group unless the hiring manager gives a job-related reason.
Write the outcome first, then five to eight duties, then required evidence, useful experience, reporting line, work terms, process, and approved pay or benefits. Use plain verbs. Do not use inflated titles, personality labels, coded language, or a long tool list where a skill would do.
Show every fact whose approval is missing. Flag requirements that may screen people out without a stated work need, but do not give employment-law advice. Route policy or legal questions to the company's people lead or counsel.
Return the intake brief, the job-description draft, removed or changed requirements with reasons, and an approval checklist. Do not publish it.
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.