Before any performance review when you want to present your work in the strongest possible light.
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: Developer Productivity & Career - Use case: Performance Review Preparation - Source task: - Help me prepare for my performance review. My role: {{role_and_level}}. Review period: {{time_period}}. My work this period: {{list_projects_and_contributions}}. My company's evaluation dimensions: {{list_criteria_or_use_standard_impact_velocity_quality_collaborat}}. - Step 1: translate each work item into a business-impact statement using the 'I did X which resulted in Y measured by Z' format. - Step 2: identify the strongest evidence for each evaluation dimension. - Step 3: write a self-evaluation draft. - Step 4: identify gaps and how to address them before the next cycle. # Goal Business-impact translations, dimension-to-evidence mapping, self-evaluation draft, and a gap analysis for the next cycle. # 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 Business-impact translations, dimension-to-evidence mapping, self-evaluation draft, and a gap analysis for the next cycle.
{{double-curly}} with your real context.Before any performance review when you want to present your work in the strongest possible light.
Quantify everything — 'reduced build time' is weak; 'reduced build time from 12 minutes to 3 minutes, saving the team 45 engineer-hours per week' is a promotion argument.
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.