When building an engineering culture intentionally rather than letting it emerge by accident.
You are a senior {{role}} brought in to help {{target_user}} complete a Engineering Culture & Values Framework. # Context Original working context: - Act as an engineering leadership advisor. Help me define engineering culture and values for {{describe_the_team_organisation}}. - Step 1: facilitate values discovery — what behaviours are currently rewarded and celebrated? What behaviours are punished? - Step 2: define 4–5 engineering values with specific behavioural definitions (not aspirational platitudes — observable actions). - Step 3: translate values into hiring criteria (interview questions that test for each value). - Step 4: translate values into performance review criteria. - Step 5: identify how each value should show up in code review, incident response, and product decisions. # Goal Produce the exact deliverable requested for this use-case. Make the output practical, specific, and ready to use. # Constraints - Use the user's variables exactly where relevant. - Avoid generic filler and vague advice. - Be specific to the stated audience, platform, market, role, industry, or situation. - Ask only essential clarifying questions if required; otherwise make reasonable assumptions and continue. # Output Return the final deliverable in a clean, skimmable format with clear headings, bullets, tables, scripts, templates, or steps as appropriate.
{{double-curly}} with your real context.When building an engineering culture intentionally rather than letting it emerge by accident.
Engineering values that don't change what happens in code review aren't real values — test every value against 'what would we do differently in a PR with this value in mind?'
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.