Sheet 4: COMMUNICATION
Category	Use Case	Prompt Template	Variables to Customize	Expected Output	Time Saved	Contributed By	Date Added	Rating
Communication	Technical to business translation	I'm a Business Analyst presenting to [STAKEHOLDER_TYPE] with [TECHNICAL_LEVEL] technical knowledge. Rewrite this technical explanation in business-friendly language: [TECHNICAL_CONTENT]. Requirements: Remove/explain jargon, use analogies, focus on business benefits (speed, cost, reliability, security), keep under 150 words.	STAKEHOLDER_TYPE, TECHNICAL_LEVEL, TECHNICAL_CONTENT	Business-friendly explanation	30-45 min	Stephen Mitchell > Claude	4-Feb	⭐⭐⭐⭐⭐
Communication	Business to technical translation	I'm a Business Analyst translating business requirements for developers. Business need: [BUSINESS_REQUIREMENT]. Convert this into technical requirements including: Functional specs, Performance criteria, Security requirements, Integration points, Data requirements.	BUSINESS_REQUIREMENT	Technical specifications	30-45 min	Stephen Mitchell > Claude	4-Feb	⭐⭐⭐⭐⭐
Communication	Status report generation	I'm a Business Analyst creating a status report for [PROJECT_NAME]. Updates: [BULLET_POINTS]. Format as executive summary including: Accomplishments this period, Upcoming milestones, Blockers and risks, Decisions needed, Overall status (Green/Yellow/Red with explanation).	PROJECT_NAME, BULLET_POINTS	Executive status report	20-30 min	Stephen Mitchell > Claude	4-Feb	⭐⭐⭐⭐
Communication	Stakeholder email drafting	I'm a Business Analyst emailing [STAKEHOLDER_TYPE] about [TOPIC]. Key points: [KEY_POINTS]. Tone: [FORMAL/PROFESSIONAL/FRIENDLY]. Purpose: [INFORM/REQUEST/ESCALATE]. Draft an email that's clear, concise, and actionable. Include: Subject line, Opening, Body with bullets, Clear ask/next steps, Professional closing.	STAKEHOLDER_TYPE, TOPIC, KEY_POINTS, TONE, PURPOSE	Complete email draft	15-20 min	Stephen Mitchell > Claude	4-Feb	⭐⭐⭐⭐
Communication	FAQ generation	I'm a Business Analyst creating FAQs for [PROJECT/FEATURE]. Documentation: [PASTE_DOCS]. Generate the top 20 questions users will likely ask during rollout. Organize by category: Basics, How-To, Troubleshooting, Advanced. Provide clear, concise answers.	PROJECT_OR_FEATURE, DOCUMENTATION	FAQ document	45-60 min	Stephen Mitchell > Claude	4-Feb	⭐⭐⭐⭐
Stakeholder Communication	Stakeholder update email	I'm a Project Manager emailing [STAKEHOLDER_TYPE] about [TOPIC] for [PROJECT_NAME]. Key points to communicate: [KEY_POINTS]. Tone: [FORMAL/PROFESSIONAL/URGENT]. Purpose: [INFORM/REQUEST/ESCALATE]. Draft an email with: Clear subject line, Brief context, Main message with bullets for key points, Specific ask or next steps, Professional closing. Keep under 200 words.	STAKEHOLDER_TYPE, TOPIC, PROJECT_NAME, KEY_POINTS, TONE, PURPOSE	Stakeholder email	20-30 min	[Name]	[Date]	⭐⭐⭐⭐⭐
Stakeholder Communication	Escalation communication	I'm a Project Manager escalating [ISSUE] to [STAKEHOLDER_LEVEL]. Issue details: [ISSUE_DESCRIPTION]. Impact: [IMPACT]. Draft an escalation email/memo including: Issue Summary (2-3 sentences), Business Impact, What We've Tried, Why Escalation is Needed, Specific Decision/Action Requested, Timeline Urgency, Risks of Inaction. Professional, fact-based tone.	ISSUE, STAKEHOLDER_LEVEL, ISSUE_DESCRIPTION, IMPACT	Escalation communication	30-45 min	[Name]	[Date]	⭐⭐⭐⭐⭐
Stakeholder Communication	Change announcement	I'm a Project Manager announcing [CHANGE_TYPE] for [PROJECT_NAME] to [AUDIENCE]. Change details: [CHANGE_DESCRIPTION]. Draft an announcement including: What's Changing (clear, specific), Why It's Changing (business rationale), When It Takes Effect, Who Is Impacted, What Actions Are Required, Where to Get Help/More Info. Reassuring but honest tone.	CHANGE_TYPE, PROJECT_NAME, AUDIENCE, CHANGE_DESCRIPTION	Change announcement	30-45 min	[Name]	[Date]	⭐⭐⭐⭐
Stakeholder Communication	Project kickoff communication	I'm a Project Manager announcing project kickoff for [PROJECT_NAME] to [STAKEHOLDER_GROUPS]. Project scope: [BRIEF_SCOPE]. Timeline: [TIMELINE]. Draft a kickoff announcement with: Project Overview (purpose and goals), Key Milestones, Team Structure, Communication Plan, How to Stay Informed, Initial Next Steps. Enthusiastic, clear, action-oriented tone.	PROJECT_NAME, STAKEHOLDER_GROUPS, SCOPE, TIMELINE	Kickoff announcement	45-60 min	[Name]	[Date]	⭐⭐⭐⭐
Stakeholder Communication	Project closure summary	I'm a Project Manager closing [PROJECT_NAME]. Project details: [PROJECT_SUMMARY]. Outcomes: [OUTCOMES_ACHIEVED]. Draft a project closure summary including: Project Overview, Original Objectives vs. Actual Outcomes, Key Metrics/Benefits Delivered, Lessons Learned (3-5 bullets), Next Steps/Ongoing Support, Thank You to Key Contributors. Professional, celebratory tone.	PROJECT_NAME, PROJECT_SUMMARY, OUTCOMES_ACHIEVED	Project closure summary	60-90 min	[Name]	[Date]	⭐⭐⭐⭐