81 Situation-specific prompts for engineering managers, directors, and VPs. Each prompt covers a recurring leadership task (status updates, roadmaps, performance reviews, incident comms) with placeholders, an example, and tuning notes.
Weekly Comms - 15 prompts
The communication layer of leadership. Status updates, stakeholder emails, launch announcements, incident comms, and more.
| # | Prompt | When to Use |
|---|---|---|
| 01 | Exec Status Update | Monday morning, synthesising team leads' updates for your VP/CTO |
| 02 | Team Weekly Summary | Friday wrap-up for your direct team |
| 03 | Stakeholder Project Update | Keeping PMs, design, and business leads aligned on delivery |
| 04 | Cross-Team Dependency Update | Flagging blockers and handoffs across teams |
| 05 | Internal Launch Announcement | Announcing a shipped feature or service to the company |
| 06 | External Launch Announcement | Customer-facing or public comms for a release |
| 07 | Team Wins Celebration | Highlighting team accomplishments to leadership and peers |
| 08 | Org Change Announcement | Communicating reorgs, new hires, or structural shifts |
| 09 | Incident Stakeholder Comms | Real-time or post-incident updates for non-technical stakeholders |
| 10 | Meeting Recap & Action Items | Turning messy meeting notes into clear follow-ups |
| 11 | Skip-Level Update | Writing upward comms for your boss's boss |
| 12 | Board Engineering Summary | Distilling engineering progress for board-level audiences |
| 13 | Engineering Newsletter | Monthly or bi-weekly update for a non-technical company-wide audience |
| 14 | Vendor Escalation Email | Escalating a blocked vendor issue in writing |
| 15 | Engineering All-Hands Agenda | Planning a quarterly or monthly all-hands meeting |
Planning Artifacts - 14 prompts
The documents that shape what gets built and when. Roadmaps, RFCs, retros, decision records, and operational playbooks.
| # | Prompt | When to Use |
|---|---|---|
| 01 | Quarterly Roadmap | Start of quarter, turning goals into a structured plan |
| 02 | RFC Outline | Proposing a technical change that needs cross-team buy-in |
| 03 | Sprint Retro Summary | Turning retro discussion into actionable themes |
| 04 | Tech Debt Prioritisation | Building a case for paying down debt with a ranked backlog |
| 05 | Build vs Buy Analysis | Evaluating whether to build in-house or use a vendor |
| 06 | Project Pre-Mortem | Identifying risks before a project starts |
| 07 | Capacity Planning | Mapping team bandwidth against committed work |
| 08 | Migration Plan | Structuring a phased approach to a system migration |
| 09 | OKR Drafting | Writing measurable OKRs from vague business goals |
| 10 | Architecture Decision Record | Documenting a technical decision with context and trade-offs |
| 11 | Incident Postmortem | Writing a blameless postmortem from timeline notes |
| 12 | Sprint Planning Breakdown | Breaking epics into well-scoped sprint tickets |
| 13 | Engineering Strategy One-Pager | Communicating what you're optimising for and why, in one page |
| 14 | Team Offsite Agenda | Planning a substantive team offsite that produces real decisions |
People Management - 16 prompts
The human side of leadership. Reviews, career conversations, hiring, and the difficult moments.
| # | Prompt | When to Use |
|---|---|---|
| 01 | Performance Review Draft | Review cycle, synthesising a half or full year of work |
| 02 | One-on-One Prep | Before your weekly 1:1 with a direct report |
| 03 | Feedback Synthesis | Combining peer feedback into a coherent narrative |
| 04 | Career Ladder Draft | Creating or refining engineering level expectations |
| 05 | Job Description | Writing a compelling, specific job posting |
| 06 | Interview Rubric | Creating structured evaluation criteria for interviews |
| 07 | PIP Documentation | Drafting a fair, clear performance improvement plan |
| 08 | Promotion Case | Building a compelling case for a direct report's promotion |
| 09 | Team Health Survey Analysis | Finding patterns and actions from survey results |
| 10 | Onboarding Plan | Creating a structured first 30/60/90 days for a new hire |
| 11 | Skip-Level Meeting Prep | Preparing for 1:1s with your reports' reports |
| 12 | Difficult Conversation Prep | Structuring hard feedback or sensitive discussions |
| 13 | Manager README | Writing a working guide to yourself for your direct reports |
| 14 | Layoff Communication | Individual and team messaging for a workforce reduction |
| 15 | Team Values Workshop | Facilitating a session to define real, usable team values |
| 16 | Staff Engineer Scope Document | Defining what a staff engineer owns and how success is measured |
Incident Management - 12 prompts
The operational backbone of engineering reliability. From alert fires through to organisational learning.
| # | Prompt | When to Use |
|---|---|---|
| 01 | Incident Commander Runbook | You're IC for a live incident and need a structured framework |
| 02 | Real-Time Status Page Update | Writing public status updates during an active incident |
| 03 | Customer Apology Email | Post-incident customer communication that rebuilds trust |
| 04 | War Room Facilitation Guide | Running an effective incident response call |
| 05 | On-Call Handoff | Handing off context at the start/end of an on-call rotation |
| 06 | Runbook Generator | Extracting operational knowledge into step-by-step runbooks |
| 07 | Incident Trend Analysis | Quarterly review of incident patterns and systemic issues |
| 08 | Remediation Tracker | Tracking postmortem action items to completion |
| 09 | Severity Classification Guide | Defining P0-P3 severity levels for your organisation |
| 10 | Game Day Plan | Planning a chaos engineering or incident simulation exercise |
| 11 | Escalation Policy Document | Defining who to call, when, and through what channel |
| 12 | Incident Readiness Review | Auditing preparedness before a launch or high-traffic event |
Architecture - 12 prompts
The technical decisions that shape your systems for years. Design, evaluate, document, and communicate architectural choices.
| # | Prompt | When to Use |
|---|---|---|
| 01 | System Design Document | Before building a new service or system |
| 02 | API Contract Design | Designing a new API (internal or external) |
| 03 | Scalability Assessment | Evaluating whether a system can handle growth |
| 04 | Data Model Design | Designing schemas for a new domain |
| 05 | Caching Strategy | Deciding what to cache, where, and how to invalidate |
| 06 | Observability Strategy | Designing monitoring, logging, and tracing for a system |
| 07 | SLO Definition | Setting Service Level Objectives for your services |
| 08 | Architecture Review Prep | Preparing to present a design for peer review |
| 09 | Dependency Mapping | Documenting service dependencies and blast radius |
| 10 | Technical Vision Document | Writing a long-term technical strategy for your area |
| 11 | Technology Radar | Evaluating and categorising technologies for your org |
| 12 | Database Selection Guide | Choosing the right database for a workload |
Hiring Pipelines - 12 prompts
The end-to-end process of finding, evaluating, and closing engineering candidates.
| # | Prompt | When to Use |
|---|---|---|
| 01 | Hiring Plan | Planning headcount and roles for a quarter |
| 02 | Recruiter Kickoff Brief | Starting a search with a recruiter |
| 03 | Sourcing Outreach Message | Cold outreach to potential candidates |
| 04 | Phone Screen Script | 30-minute initial candidate screen |
| 05 | Take-Home Exercise Design | Creating a fair, well-scoped assessment |
| 06 | Interview Debrief Facilitation | Running a structured hiring decision meeting |
| 07 | Candidate Evaluation Summary | Synthesising interview feedback into a decision |
| 08 | Offer Justification | Building the case for a specific comp package |
| 09 | Candidate Closing Pitch | Selling the role to a finalist who's deliberating |
| 10 | Rejection Email | Delivering a respectful, useful no |
| 11 | Pipeline Analytics Review | Analysing funnel metrics to improve hiring |
| 12 | Interviewer Calibration Guide | Training interviewers for consistency |
Each file follows the same format:
## Situation - When to use it
## The Prompt - Copy-paste ready, with [PLACEHOLDERS]
## Example Input
## Example Output
## Tuning Notes
- V1: 36 prompts across comms, planning, and people management
- V2: Additional categories (incident management, architecture, hiring pipelines)
- V2: CLI tool via Claude Code (
ai-eng fetch postmortem --timeline "...") - V3: Prompt chaining (multi-step workflows)
- V3: Org-size variants (startup, growth, enterprise)