Launch FAQ Generator

# Task
Create launch FAQs using ONLY the provided launch information.

# Inputs
- Launch context: {launch_context}
- Audience: {audience}
- Feature or product: {feature_or_product}
- Known questions: {known_questions}
- Goal: {goal}
- Constraints: {constraints}

# Anti-hallucination rules
1. Only answer questions based on the provided context. No invented features or timelines.
2. If an answer is uncertain, mark it [NEEDS CONFIRMATION] and write the best-available response.
3. Do not promise functionality or dates not stated in the inputs.

# FAQ segmentation
Create separate FAQ sections for each audience type:
- **Customer-facing**: What users see and experience. Avoid internal jargon.
- **Internal (sales/CS)**: Positioning, objection handling, competitive context.
- **Internal (technical)**: Architecture decisions, known limitations, migration details.
Only generate sections relevant to the stated audience.

# Timing groups
Within each section, organize questions by urgency:
- **Day 1** (launch day): What people will ask immediately.
- **Week 1** (first week): Follow-up questions as people start using it.
- **Ongoing**: Questions that will persist.

# Per FAQ item
- Question (written as the audience would actually ask it)
- Answer (clear, specific, under 3 sentences)
- If the question maps to a common objection, add: **Objection angle**: [the underlying concern] and **Reframe**: [how to address it]

# Output
1. FAQ intro (2-3 sentences: what this FAQ covers and who it's for)
2. Segmented FAQs (by audience, then by timing)
3. Gaps: 3-5 questions you expect but can't answer from the inputs — flag for the launch team

<context>
  <launch_context>{launch_context}</launch_context>
  <audience>{audience}</audience>
  <feature_or_product>{feature_or_product}</feature_or_product>
  <known_questions>{known_questions}</known_questions>
  <goal>{goal}</goal>
  <constraints>{constraints}</constraints>
</context>
<task>Create launch FAQs using ONLY the provided information.</task>
<instructions>
  No invented features or dates. Mark uncertain answers [NEEDS CONFIRMATION].

  Segment by audience: customer-facing, internal sales/CS, internal technical. Only relevant sections.

  Within each: Day 1, Week 1, Ongoing groups.

  Per FAQ: question (as audience would ask), answer (<3 sentences). If maps to objection: add objection angle and reframe.
</instructions>
<output>
  Return: FAQ intro, segmented FAQs by audience and timing, and 3-5 gap questions for the launch team.
</output>

Launch context: {launch_context}
Audience: {audience}
Feature or product: {feature_or_product}
Known questions: {known_questions}
Goal: {goal}
Constraints: {constraints}

Rules: only provided info, mark uncertain answers [NEEDS CONFIRMATION], no invented dates.

Segment by audience (customer / sales-CS / technical). Group: Day 1, Week 1, Ongoing. Per FAQ: question, answer (<3 sentences), objection angle + reframe if applicable.

Based on the entire content above, return: FAQ intro, segmented FAQs, and 3-5 gap questions.