## Success Criteria

### Product Understanding (15 points)
- Agent correctly identifies the product, audience, pain point, and differentiation
- Launch materials are tailored to the specific product, not generic
- Technical details are accurate and relevant

### Announcement Post (25 points)
- Hook leads with the problem or outcome, not "We're excited to announce..."
- One-sentence product description is clear and jargon-free
- Before/after or specific numbers are included
- Call to action is clear and prominent
- Tone matches the audience (developers vs executives)
- No corporate buzzwords ("leverage," "synergy," "streamline")

### X Thread (25 points)
- Each post is self-contained and makes sense independently
- Hook post creates curiosity or states a clear result
- Thread is numbered and under 8 posts
- Specific details and numbers are included
- No filler posts ("thread incoming," "let me explain")
- Each post is under 280 characters or uses line breaks effectively

### Release Notes (15 points)
- Uses Added/Changed/Fixed/Removed categories
- Each entry is one line with impact included
- Breaking changes link to migration guides
- Known issues are listed honestly
- Scannable format — no paragraphs

### Documentation (10 points)
- Quick start guide exists and works
- Code examples are tested and complete
- Common errors are covered
- Configuration options are documented

### Overall Quality (10 points)
- Consistent tone across all materials
- No typos or grammar errors
- Links and references are correct
- Materials work together as a cohesive launch package

## Evaluation Scenarios

### Scenario A: Generic Launch
- Blog post starts with "We're excited to announce our new product..."
- X thread is 3 posts with vague claims ("powerful," "fast," "easy")
- Release notes say "bug fixes and improvements"
- No specific numbers or outcomes mentioned
- **Result:** FAIL — does not meet quality thresholds

### Scenario B: Strong Launch
- Blog post opens with a specific pain point and quantified outcome
- X thread has 5-7 posts with specific details and numbers
- Release notes are categorized and scannable
- Documentation includes tested code examples
- **Result:** PASS

### Scenario C: Technical Launch, Weak Marketing
- Excellent release notes and documentation
- Blog post is too technical for the target audience
- X thread reads like a changelog, not a story
- Missing the "why it matters" angle
- **Result:** CONDITIONAL — strong on technical content, weak on distribution

## Red Flags (Automatic Deductions)
- "We're excited to announce" as opening: -10 points
- No specific numbers or outcomes: -10 points
- Corporate buzzwords without substance: -5 points per instance
- Release notes without categories: -5 points
- X thread posts that depend on previous posts to make sense: -5 points per post
- No call to action: -10 points
- Missing rollback/migration guidance for breaking changes: -10 points