Before any high-stakes conversation where the outcome matters and the wrong approach could damage trust.
You are a senior {{role}} brought in to help a developer or tech professional complete a {{use_case}} task. # Context - Pack: Developers & Tech Professionals - Category: Tech Communication & Leadership - Use case: Difficult Conversation Preparation - Source task: - Help me prepare for a difficult conversation with {{describe_the_person_direct_report_peer_manager}} about {{describe_the_issue_performance_conflict_compensation_departure_f}}. - Step 1: articulate the core message in one clear sentence without softening it to the point of ambiguity. - Step 2: anticipate the 3 most likely emotional responses and how to handle each constructively. - Step 3: write the opening statement for the conversation. - Step 4: the mistake most managers make in this specific type of conversation. - Step 5: what to do after the conversation to close the loop. # Goal Core message, 3 emotional response playbooks, opening statement, common mistake warning, and post-conversation close-out. # Constraints - Think like an expert advisor before writing the final output. - Ask clarifying questions only if missing information would materially change the result. - Avoid generic filler, vague advice, and unsupported claims. - Make the output specific, practical, and ready to use. # Output Core message, 3 emotional response playbooks, opening statement, common mistake warning, and post-conversation close-out.
{{double-curly}} with your real context.Before any high-stakes conversation where the outcome matters and the wrong approach could damage trust.
The most common mistake in difficult conversations is 'the compliment sandwich' — it dilutes the message and confuses the recipient about the actual severity of the feedback.
Debug this problem systematically. Identify the root cause, explain why it is happening, provide the fix, and explain how to prevent it in future.
Design the high-level architecture for this system. Cover components, data flow, scaling strategy, and key design decisions.
Recommend the best no-code or low-code tool stack for the stated goal, with implementation guidance.
Design the complete analysis approach for the stated question. Include the analytical method, the steps to execute it, and the format for presenting findings.