When miscommunication between engineering and other functions is slowing delivery or creating frustration.
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: Cross-Functional Communication Strategy - Source task: - Help me build a communication strategy for the engineering team's relationships with {{describe_stakeholders_product_design_marketing_sales_executives}}. - Step 1: for each stakeholder group, define what they need from engineering (certainty, speed, quality signal, technical context), and what engineering needs from them. - Step 2: design the communication cadence (recurring syncs, async updates, escalation paths). - Step 3: write a template for the 3 most important communications: engineering update for leadership, technical context briefing for product, and incident communication for all stakeholders. # Goal Per-stakeholder needs analysis, communication cadence design, and 3 communication templates. # 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 Per-stakeholder needs analysis, communication cadence design, and 3 communication templates.
{{double-curly}} with your real context.When miscommunication between engineering and other functions is slowing delivery or creating frustration.
Stakeholders don't want technical details — they want certainty about outcomes and timelines. Translate technical status into business impact in every communication.
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.