When scaling security beyond a central security team to embed it in every engineering team.
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: Cybersecurity & Privacy - Use case: Security Champions Programme Design - Source task: - Design a Security Champions programme for an engineering organisation of {{size}} developers across {{number}} teams. - Step 1: define the Security Champion role (responsibilities, time commitment, selection criteria). - Step 2: design the onboarding and training curriculum (what champions must learn in their first 90 days). - Step 3: create the toolkit for champions (secure code review checklist, threat model template, vulnerability triage guide). - Step 4: design the community of practice (meeting cadence, knowledge sharing, recognition). - Step 5: measure programme success : what metrics show the programme is improving security outcomes. # Goal Role definition, 90-day training curriculum, champion toolkit, community of practice design, and programme success metrics. # 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 Role definition, 90-day training curriculum, champion toolkit, community of practice design, and programme success metrics.
{{double-curly}} with your real context.When scaling security beyond a central security team to embed it in every engineering team.
Security Champions fail when they're treated as the security team's outstretched hand — they succeed when they're empowered to represent engineers' security needs back to the security team.
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.