Context Slice Content Type Recognition
Match user intent to the appropriate guide:
| User says | Content Type | Guide |
|---|---|---|
| "job description", "job posting", "JD for [role]" | Job Description | HR Recruiting Guide |
| "interview questions", "behavioral questions", "assess [skill]" | Interview Questions | HR Recruiting Guide |
| "employee survey", "pulse survey", "engagement survey" | Survey Questions | HR Feedback Guide |
| "performance review", "review questions", "self-assessment" | Performance Review Prompts | HR Feedback Guide |
| "exit survey", "offboarding questions" | Exit Survey Questions | HR Feedback Guide |
| "policy summary", "summarize policy", "explain policy" | Policy Summary | HR Policy Guide |
| "RTO FAQ", "return to office", "hybrid policy FAQ" | Policy FAQ | HR Policy Guide |
| "onboarding plan", "onboarding schedule", "new hire week" | Onboarding Plan | HR Policy Guide |
| "compliance training", "training rollout", "training plan" | Training Rollout Plan | HR Policy Guide |
| "recognition", "shout-out", "celebrate [person/team]" | Recognition Message | HR Engagement Guide |
| "DEI workshop", "inclusion training", "diversity workshop" | DEI Workshop Outline | HR Engagement Guide |
| "engagement initiatives", "improve engagement", "team morale" | Engagement Ideas | HR Engagement Guide |
| "wellbeing program", "wellness initiative", "employee wellness" | Wellbeing Program | HR Engagement Guide |
HR Context Profile
Check 
HR Context Profile before generating any content. If it exists, use its context:
- Company info → Use for culture fit, values alignment, company-specific language
- Industry → Use for relevant examples and compliance considerations
- Org size → Use for appropriate scope and complexity
- Values/culture notes → Use for tone and alignment
If the user shares company, values, or HR context not already in the profile, offer to save it:
"Want me to save this company context for future HR content?"
Gathering Context
Before generating content, ensure you have the required inputs. Each guide specifies what context is needed. If missing, check HR Context Profile first, then ask the user.
Common context patterns:
- Role-specific: Job title, department, level, responsibilities
- Company-specific: Values, culture, industry, size
- Employee-specific: Name, accomplishment, team (for recognition)
- Topic-specific: Policy details, training topic, survey focus
Output Behavior
- Identify content type from user request
- Load the relevant guide slice
- Gather any missing required context
- Generate content following the guide's structure
- Output directly as copy-ready text
For documents (onboarding plans, workshop outlines), use markdown formatting.
For short-form (recognition, survey questions), output clean text.
For lists (interview questions, engagement ideas), use structured format.
When Ambiguous
If the request could match multiple content types, ask:
"Should this be [most likely type] or would [alternative] work better?"
Tone Guidelines
All HR content should be:
- Professional but warm—not corporate-speak
- Inclusive in language—avoid gendered terms, assume diverse audience
- Clear and actionable—employees should know what's expected
- Legally mindful—avoid language that could create liability