15 Essential ChatGPT & Claude Prompts for Project Managers and Tech Leads

Act as a Senior Technical Product Manager. Break down the following epic into technical user stories for a 2-week sprint: [Insert Epic / Feature Description]. For each user story, provide:

Act as a Principal Engineer and Project Risk Manager. We are about to start a new project with the following scope and tech stack: [Insert Project Overview & Stack]. Conduct a Pre-Mortem analysis assuming this project failed 6 months from now. List the top 7 technical and operational risks, group them into High, Medium, and Low impact, and provide a concrete mitigation strategy for each.

Act as a Lead Solution Architect. Convert this high-level feature proposal into a structured Technical Requirements Document (TRD): [Insert Feature Idea / Product Brief]. Include:

Act as an Agile Scrum Master. Help me plan our next sprint based on these parameters: Team Size & Capacity [e.g., 4 devs, 60 total story points], Carryover Tasks [list], New Backlog Candidates [list], Sprint Goal [state the objective]. Select and prioritize the optimal set of tasks to achieve the Sprint Goal without exceeding capacity, accounting for code reviews, testing overhead, and a 10% buffer for unexpected bugs.

Act as an Engineering Manager. Analyze these daily standup notes from my team: [Paste Raw Standup Notes / Chat Logs]. Summarize key progress in 3 bullet points, extract all active blockers and who is blocked by what/whom, and provide an action plan to unblock the team.

Act as a Technical Lead. I have a list of technical debt items: [Insert Tech Debt List]. Categorize each item using a 2x2 matrix (High/Low Impact × High/Low Effort). For the top 2 urgent items, write a brief business justification explaining to a non-technical PM why resolving this debt increases long-term velocity.

Act as a VP of Engineering. Convert the following technical updates into a concise Executive Status Report for C-level leadership: [Insert Jira Exports, Release Notes, or Dev Updates]. Structure the output as: Executive Summary (2 sentences max), Key Accomplishments This Week, Milestones & Roadmap Status (On Track / At Risk / Off Track), and Key Blockers & Needed Executive Support.

Act as a Director of Project Management. I need to write an email to a stakeholder asking for a critical scope addition mid-sprint without pushing back the release date. Context: [Explain request and trade-offs]. Draft a polite, diplomatic, but firm response that explains the trade-offs (the Iron Triangle: Time, Scope, Cost) and presents two viable alternatives without sacrificing quality.

Act as a Technical Content Strategist. Convert these git commit logs and pull requests into user-friendly Release Notes: [Paste Git Commits / PR Titles]. Group them into New Features, Improvements & Performance, and Bug Fixes.

Act as an Agile Coach. Analyze the raw feedback from our team's Sprint Retrospective: What Went Well [paste], What Didn't Go Well [paste], What We Can Improve [paste]. Identify the top 3 recurring themes and propose 3 SMART (Specific, Measurable, Achievable, Relevant, Time-bound) action items for the next sprint.

Act as a Systems Reliability Engineer and Process Lead. We experienced the following incident/delay: [Describe Incident / Missed Deadline]. Conduct a blameless 5-Whys root-cause analysis, identify the true root cause (not just the symptom), and propose two process safeguards that would have caught this earlier.

Act as an Engineering Manager. Create a 30-60-90 day onboarding checklist for a new Senior Full-Stack Engineer joining our team. Tech Stack & Tools: [Insert Stack], Project Context: [Insert Project Info]. Break goals into Day 1-30 (Learning & First PR), Day 31-60 (Independent Ownership), and Day 61-90 (Leadership & Optimization).

Act as a Technical PM. Help me evaluate two competing tools/APIs for our platform: Option A [Insert Tool A], Option B [Insert Tool B], Core Requirements [Insert Requirements]. Generate a comparison table covering Cost Structure, Developer Ergonomics, Scalability, Maintenance Overhead, and Lock-in Risk, and end with a recommended pick.

Act as a Technical Communicator. Explain the following complex technical concept/issue to non-technical business stakeholders: [Insert Technical Explanation or Architecture Problem]. Use an intuitive real-world analogy, avoid engineering jargon, and focus entirely on business impact, timeline, and value.

Act as an AI Systems Architect. Format this task so an autonomous AI Agent connected via MCP can execute it without human intervention: [Describe Desired Code Change / Feature]. Format the response as a strict Markdown specification with: Clear Goal, File Paths & Targets, Step-by-Step Execution Plan, and Verification & Testing Criteria for the Agent.