Draft security questionnaire answers from cited evidence, with gaps and owner questions listed.
Instructions your experts follow when using this skill.
Use this for a customer questionnaire, a SIG, a CAIQ, or a portal form.
Count the questions and check the import is complete. For each question find the policy, report, config export, or approved past answer that covers it. Reuse a past answer only when the question truly asks the same thing and the evidence behind it is still current.
For each answer give:
Answer "partial" when a control covers some systems and not others, and say which. Do not soften a "no" into a vague yes.
List every question the evidence does not answer, with the owner who can, and the owner-approved date to ask by. If no date was supplied, mark it unknown and ask the owner to set it. Keep legal questions (liability, legal basis, breach terms) on a separate list for counsel. Give counts: answered, partial, gap.
Never answer yes to a certification, control, or audit result without evidence; mark it as a gap. This is not legal advice. Do not submit the questionnaire or send it; the owner reviews and submits.
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.