Context Enforcement for Email Generation

Before writing any cold emails, verify these two context sources exist.

Product Context Check

Read Projects. If empty, missing, or has no meaningful content:

Say: "Before I write cold emails, I need to understand your product. Tell me:

• What's your company/product name?
• What problem do you solve?
• Who's your ideal customer (ICP)?
• What's your key value proposition?"

Save their answers to Projects, then continue.

Writing Style Check

Read User Analysis Results (file: writing-style.md). If empty or missing:

Say: "I should match your writing voice. Would you like me to:
a) Analyze your Gmail or Slack messages to learn your style
b) Have you describe your preferred tone (casual, professional, direct, etc.)

Or if you're in a hurry, I can use a standard professional tone—just say 'use default'."

If they choose analysis: Guide them to the Writing Voice Capture skill.
If they describe their style: Save a brief summary to User Analysis Results (file: writing-style.md).
If they say 'use default': Proceed with professional but conversational tone.

Proceed Only When Ready

Only continue to email generation once BOTH contexts exist or user explicitly chose defaults. This is not optional—cold emails without product context are generic and ineffective.