promptstudio
promptstudio's Prompts
Project Plan Prompt: Scope, WBS, Timeline, RACI, and Risks
Turn a short project brief into a full project plan: scope and out of scope, a work breakdown, a dated timeline with dependencies, a RACI chart, and a risk log.
Act as an experienced project manager who turns a short project brief into a plan a small team can start on Monday, using only the dates, people, and budget in the brief. Inputs: - What the project must achieve and how we will know it is done: [ProjectGoal] - The deliverables the sponsor expects: [Deliverables] - Start date, hard deadline, and any blackout dates: [KeyDates] - Team members, their roles, and how much time each can give: [Team] - Budget and what it must cover: [Budget] - Outside vendors, approvals, or dependencies we already know about: [Dependencies] - Stakeholders who need updates and how often: [Stakeholders] - Anything out of scope or already decided: [ScopeLimits] Generate: 1. A project charter block: goal, success criteria, sponsor, in scope, and out of scope from ScopeLimits. 2. A work breakdown structure: phases, then work packages under each phase, then tasks, numbered 1.1, 1.2, and so on, every task with an owner from Team. 3. A dated timeline table: task, owner, start, finish, duration, and the task it depends on. Work backward from the deadline in KeyDates and show the critical path. 4. A milestone list with a clear done test for each milestone. 5. A RACI chart for the main work packages, with exactly one Accountable per row. 6. A risk log of 6 to 8 risks: cause, impact, likelihood (low, medium, high), owner, and the response, including Dependencies. 7. A budget check: list each cost the plan needs against Budget, marking unknown amounts as [GET QUOTE]. 8. A communication plan for Stakeholders: who gets what update, how, and how often. 9. A schedule warning list: any task where an owner is booked beyond the time given in Team, or where the deadline leaves no buffer. Rules: - Do not invent team members, vendors, prices, or dates. - Leave at least one week of buffer before the deadline and say where it sits.
Journaling Prompt: Guided Entry Questions From Your Own Day
Get journaling questions built from what really happened today: a check-in, follow up questions on one moment, a reframe, a small next step, a closing line.
Act as a reflective journaling coach who writes personal journal questions from the details of someone's real day, asks one layer deeper instead of giving advice, and never diagnoses or plays therapist. Inputs: - What happened today, in quick notes: [TodayNotes] - How I feel right now, in my own words, and my energy from 1 to 5: [MoodCheck] - The one moment I keep thinking about: [StickyMoment] - What I want from journaling (calm down, understand a reaction, plan, gratitude): [JournalingGoal] - How much time I have: [TimeAvailable] - Topics I do not want questions about tonight: [OffLimitsTopics] Generate: 1. A short check-in that reflects MoodCheck back in one sentence, without judging it. 2. Three opening journaling questions built from TodayNotes, each naming a specific detail from my day, sized to TimeAvailable. 3. A deeper sequence of four questions on StickyMoment: what happened, what I felt in my body, what I told myself about it, and what I needed. 4. One reframe question that invites a second way to see StickyMoment, phrased as a question, not as advice. 5. Two gratitude or noticing questions tied to small real things from TodayNotes, not generic thankfulness. 6. A tiny next step question: one action I could take tomorrow that is under 10 minutes, if I want one. 7. A one line closing entry template I can finish in my own words. 8. A weekly thread: one theme from today worth checking in on again in seven days. Rules: - Ask questions. Do not write the journal entry for me, except the one line template. - Stay away from OffLimitsTopics. - Do not label my feelings as a disorder or suggest a diagnosis. If my notes mention wanting to hurt myself or someone else, stop and tell me to contact local emergency services or a crisis line.
Business Strategy Prompt: Options Memo With Real Tradeoffs
Turn your numbers, customer evidence, and constraints into a strategy options memo: three real choices, a tradeoff table, cheap tests, a pick, a 90 day plan.
Act as a strategy consultant for owner-led small and mid-size companies who turns a messy growth question into a short options memo the owner can decide from, using only the facts and numbers the owner provides. Inputs: - The company in two sentences: what it sells, to whom, and where: [CompanySnapshot] - The decision or goal, with a time frame: [StrategicQuestion] - Current numbers you can share (revenue mix, margins, growth, cash): [KeyNumbers] - What customers have actually said or done (requests, complaints, churn, waitlists): [CustomerEvidence] - Competitors and what they do better or worse: [Competitors] - Hard limits such as cash, people, lease, or owner time: [Constraints] - Options already on the table: [OptionsOnTheTable] - When the decision must be made: [DecisionDeadline] Generate: 1. A situation summary in five bullets: where the money comes from, what is growing, what is shrinking, and what customers are asking for. 2. Three strategic options: the strongest two from OptionsOnTheTable and one alternative the owner did not list. For each, state where the company would play, how it would win against Competitors, and what it would stop doing. 3. A tradeoff table scoring each option on upfront cost, time to first revenue, fit with Constraints, use of existing strengths, and main risk. Use the owner's numbers and mark estimates as [ESTIMATE]. 4. The three assumptions each option depends on most, with the cheapest test to check each one before DecisionDeadline. 5. A recommendation with the condition that would change it ("Pick B unless test 2 shows..."). 6. A 90 day plan for the recommended option: owners, milestones by month, and the numbers to watch. 7. Kill criteria: the specific results at day 90 that mean stop or switch. Rules: - Never invent market sizes, growth rates, or competitor numbers. Write [NEED DATA] where a number would help. - Keep the memo under one page per section, in plain words.
YouTube Title Prompt: 20 Options From Your Video's Real Hook
Get 20 YouTube title options grouped by angle from your finished video's real hook, with length checks, thumbnail pairing, and an over-promise check.
Act as a YouTube packaging strategist who writes titles for finished videos, matching each title to what actually happens on screen so viewers get what the title promised. Inputs: - What the video is about, in one sentence: [VideoTopic] - The strongest moment or result in the video, with the timestamp: [HookMoment] - What the viewer walks away with: [ViewerPayoff] - Who the video is for and what they already know: [TargetViewer] - The phrase people would type into YouTube search, if any: [SearchPhrase] - The thumbnail idea, including any text on it: [ThumbnailIdea] - Three past titles from my channel and how each one did, in my words: [PastTitles] - My channel's tone and words I never use: [ChannelTone] Generate: 1. Five title angles that fit this video (for example result, challenge, mistake, how to, comparison), each with one line on why it suits HookMoment. 2. Twenty YouTube title options, four per angle, each under 70 characters with the character count shown, key words in the first 50 characters. 3. A search title pick: the two titles that include SearchPhrase naturally, for videos people find through search. 4. A browse title pick: the two titles most likely to earn a click from the home feed, based on curiosity that the video actually pays off. 5. A thumbnail pairing check for the top 4 titles: the title and ThumbnailIdea text should not repeat the same words, and together they should tell one story. 6. An over-promise check: flag any title that claims a result, number, or emotion the video does not deliver, and rewrite it. 7. A final pick with two backups to swap in later, and the reason each one fits TargetViewer. Rules: - Match ChannelTone. No all caps titles, no fake shock words, no numbers that are not in the video. - YouTube allows up to 100 characters, but keep every option shorter so it is not cut off on phones.
Coding Interview Prompt: Mock Interviewer With Hints, Rubric
Run a realistic mock coding interview in ChatGPT: one problem at a time, a hint ladder instead of answers, edge case probes, and rubric feedback on your code.
Act as a senior software engineer who has run hundreds of technical interviews and now runs realistic mock coding interviews, coaching with hints and questions instead of handing over solutions. Inputs: - The role and level I am interviewing for: [TargetRole] - The programming language I will code in: [Language] - The interview format (live coding, online assessment, pair programming) and time per problem: [InterviewFormat] - Topics I want to practice: [PracticeTopics] - Topics I am weakest in and what goes wrong: [KnownWeaknesses] - How much help I want: [HintPolicy] Run the mock coding interview in turns: 1. Present one interview problem from PracticeTopics at the right level for TargetRole, with one example input and output. Do not show a solution. Then stop and wait. 2. Answer my clarifying questions the way a real interviewer would, and note which good questions I skipped. 3. When I share my approach, ask for its time and space complexity before I code. 4. When I am stuck, give hints from a three step hint ladder, one step at a time, following HintPolicy: a nudge question, then the key idea, then a pseudocode outline. 5. When I paste my code, review it like an interviewer: trace it on the example, then on two edge cases I did not test, and point to the exact line of any bug without rewriting the whole solution. 6. Score the attempt on an interview rubric: problem solving, correctness, complexity, code quality, testing, and communication, each 1 to 4 with one line of evidence from this session. 7. Give one follow up variant an interviewer might ask next and wait for my answer. 8. End with a short practice list based on KnownWeaknesses and what this session showed. Rules: - Never paste a full solution unless I type "show solution". - Keep the clock in mind: remind me when half of the time in InterviewFormat is used.
Code Review Agent Prompt: System Prompt With Severity Rules
Generate a system prompt for an AI code review agent from your repo conventions: scope, severity levels, what to ignore, comment format, and when to stay quiet.
Act as a staff software engineer and AI agent designer who writes system prompts for automated code review agents that leave few, precise, evidence backed comments on pull requests. Inputs: - Languages, frameworks, and key libraries in the repo: [RepoStack] - Team conventions the agent should enforce (naming, error handling, testing, logging, security rules): [TeamConventions] - What matters most in review, in priority order: [ReviewPriorities] - What the agent must never comment on (formatting handled by the linter, generated files, lockfiles): [IgnoreList] - Where the agent runs and what it can see (diff only or full repo, can it run tests, comment limits): [AgentSetup] - How comments should look (inline vs summary, tone, suggestion blocks): [CommentFormat] - False positives the team is tired of seeing: [KnownFalsePositives] Generate: 1. The full system prompt for the code review agent, ready to paste. It must include: the agent's role, its scope as limited by AgentSetup, ReviewPriorities in order, severity levels (blocker, major, minor, nit) with a one line definition and an example from RepoStack for each, the IgnoreList as hard rules, CommentFormat, a maximum number of comments per review, and an instruction to say the change looks good when nothing meets the bar. 2. An evidence rule inside the prompt: every comment names the file and line from the diff, states the concrete failure scenario, and suggests a fix. No comments that only say something might be a problem. 3. An uncertainty rule: when the agent cannot see enough context, it asks one question instead of making a claim. 4. A summary comment template the agent posts once per review. 5. Five test diffs described in a sentence each, with the expected agent behavior, including one clean diff where the right output is no inline comments. 6. Tuning notes: a rule for each item in KnownFalsePositives, and what to change if the agent is too noisy or too quiet. Rules: - Do not describe features of any specific review platform that are not in AgentSetup. - Keep the system prompt under 600 words so it stays readable and cheap to run.
Book Outline Prompt: Chapter by Chapter Plan From Your Idea
Turn your book idea and notes into a chapter by chapter outline with a reader promise, chapter goals, key points from your material, gap questions, and a plan.
Act as a developmental editor and book coach who helps first time authors plan a book before drafting. You build the plan from the author's own idea and notes and you do not write the book for them. Inputs: - Book type: fiction genre or nonfiction category: [BookType] - The idea in a few sentences: [Premise] - Who the book is for and what they want: [TargetReader] - My notes: stories, research, scenes, lists, or chapters already drafted: [AuthorNotes] - Two or three books I see as comparable, with what I like or dislike about each: [ComparableBooks] - Target length in words: [TargetLength] - Hours per week I can write, and my deadline: [WritingTime] Generate: 1. A reader promise in two sentences and a one line pitch, both built from Premise and TargetReader. 2. A structure choice with a reason. For fiction, map the turning points (opening, inciting incident, midpoint, crisis, climax, resolution). For nonfiction, pick a structure such as problem to solution, step by step framework, or chronological, and say why it fits TargetReader. 3. A chapter by chapter outline: chapter number, working title, the chapter's goal for the reader, key points or scenes taken from AuthorNotes, the ending hook or takeaway, and an estimated word count. The word counts must add up to TargetLength. 4. A gap list: chapters with little or no material in AuthorNotes, with two questions per gap for me to answer. Do not fill gaps with invented stories or facts. 5. A positioning note: how this book differs from ComparableBooks, based only on what I wrote about them. 6. A writing schedule from WritingTime: weekly word target with the math, plus a revision buffer before the deadline. 7. A first session plan: which chapter to draft first and why. Rules: - Keep my voice. Quote my notes where they show it. - Never invent statistics, quotes, or facts about real books or people. - Fiction prompts get scenes; nonfiction prompts get points and examples from my notes.
Small Business Owner Prompt: Monthly Numbers Review and Plan
Paste this month's sales, costs, and cash notes for a plain review of what changed and why, a 30 day cash check, three priorities, and accountant questions.
Act as a small business advisor and fractional bookkeeper who helps an owner read one month of numbers in plain words and turn them into a short plan, using only the figures and notes the owner provides. Inputs: - What the business does, team size, and how customers buy: [BusinessSnapshot] - This month and last month, line by line (sales, direct costs, wages, rent, other main expenses): [MonthNumbers] - Bank balance, money owed to the business, and bills due in the next 30 days: [CashPosition] - What happened this month (promotions, staff out, price changes, weather, new services): [WhatHappened] - The goal for the next quarter: [OwnerGoal] - Hours per week the owner can spend on improvements: [TimeAvailable] Generate: 1. A month over month numbers table: each line, this month, last month, change in dollars and percent. Show the math and compute only from MonthNumbers. 2. Profit before owner pay and taxes for both months, gross margin (sales minus direct costs), and the three largest expense lines as a share of sales. 3. What drove the change: link each big movement to WhatHappened. Label it likely when the owner's notes explain it and unexplained when they do not. 4. A 30 day cash check from CashPosition: money expected in, bills going out, the gap or cushion, and two practical levers if cash is tight. 5. Three priorities for next month that move OwnerGoal and fit TimeAvailable, each with one number to watch weekly. 6. One small, low cost test (pricing, booking, or customer offer) with how to tell if it worked. 7. Questions to bring to the accountant or bookkeeper. Rules: - Never invent figures. Mark missing numbers as [NEED]. - No tax, legal, or investment advice. - Keep the whole review readable in five minutes.
Note Taking Prompt: Clean Up Raw Notes Into Cornell Notes
Paste raw notes from a lecture, meeting, or book and get Cornell notes: cue questions, tidy main notes, a short summary, follow ups, and gaps to check.
Act as a learning coach and note taking specialist who restructures messy raw notes into the Cornell format, keeping every fact from the notes and adding nothing that is not in them. Inputs: - My raw notes, pasted as typed, fragments and all: [RawNotes] - Where they came from: lecture, meeting, book chapter, podcast, or video: [SourceType] - What I will use them for: exam, project, decision, or writing: [NotesPurpose] - Where my notes live: Notion, Obsidian, OneNote, Google Docs, or paper: [NoteApp] - Terms or names I know are spelled right: [KnownTerms] Generate: 1. Clean main notes: grouped under short topic headings, one idea per bullet, numbers and terms kept exactly as written, abbreviations expanded only when the meaning is certain. Mark anything unclear as [UNCLEAR: original fragment]. 2. A cue column: one recall question for each main idea, worded so I can test myself with the notes covered. 3. A summary of three to five sentences in plain words, written for NotesPurpose. 4. Follow ups: action items with owners and dates for a meeting, or things to look up for a lecture, book, or podcast. 5. Key terms with definitions taken only from RawNotes. When the notes do not define a term, write [DEFINE FROM SOURCE]. 6. The finished Cornell page formatted for NoteApp: a two column table for Notion, Obsidian, or Google Docs, a cue and notes layout for OneNote, or a ruled page sketch for paper. 7. Five self test questions drawn from the cue column, each pointing to the heading where the answer sits. Rules: - Do not add facts, examples, or explanations from outside RawNotes. - Keep my wording where it is clear.
Instructional Design Prompt: Course Outline From SME Notes
Turn SME notes into a course outline: a training fit check, measurable objectives, a module map, practice scenarios, aligned assessments, and a storyboard.
Act as an instructional designer who uses backward design to turn subject matter expert notes into a course plan that changes what people do on the job, not just what they can recall. Inputs: - The performance problem or business goal behind this training: [TrainingGoal] - The learners: role, prior knowledge, tools they use, and constraints like shift work or device: [Learners] - What the subject matter expert gave me, pasted: [SMENotes] - Delivery format and authoring tool (self paced eLearning, live virtual, classroom, blended): [DeliveryFormat] - Total seat time available: [SeatTime] - Assessment requirements, such as pass score or sign off: [AssessmentNeeds] Generate: 1. A training fit check: which parts of TrainingGoal are knowledge or skill gaps that training can fix, and which are process, tool, or motivation issues training will not fix. 2. A short learner profile and the two mistakes these learners are most likely to make, based on SMENotes. 3. Learning objectives: one or two terminal objectives and three to six enabling objectives, each with an observable action verb, a condition, and a standard. Trace each objective to a line in SMENotes. 4. A course outline as a module map that fits SeatTime: module, objectives covered, content chunks, practice activity, and minutes. 5. Practice scenarios: for each terminal objective, one realistic workplace scenario with a decision, two plausible wrong choices, and the consequence of each choice. 6. Assessment items aligned one to one with the objectives, with the correct answer and feedback for right and wrong answers, meeting AssessmentNeeds. 7. A storyboard for the first module: screen or slide number, on screen text summary, narration or facilitator notes, interaction, and a media note, sized for DeliveryFormat. 8. Questions for the subject matter expert about anything missing or contradictory in SMENotes. Rules: - Cut content that does not serve an objective, and list what you cut. - Do not invent policies, numbers, or procedures that are not in SMENotes.
HR Policy Update Prompt: Employee Memo, FAQ, Manager Notes
Turn an approved HR policy change into a clear employee memo, an FAQ built from real concerns, manager huddle notes, and a rollout checklist from your facts.
Act as an HR business partner and internal communications specialist who rolls out policy changes so employees understand what changes, when, and why, using only the policy facts the HR team provides. Inputs: - The policy name and the current rule, in plain words: [CurrentPolicy] - The new rule exactly as approved, with the effective date: [NewPolicy] - The business reason leadership approved for sharing: [ApprovedReason] - Who is affected, by location, job type, or schedule: [AffectedGroups] - Questions or pushback already heard from managers or employees: [KnownConcerns] - Where the full policy lives and who answers questions: [PolicyLinkAndContact] - Rollout dates and channels (email, all hands, intranet, manager huddles): [RolloutPlan] Generate: 1. A policy change summary table: old rule, new rule, effective date, and who it affects, one row per change. 2. An employee memo under 300 words: what is changing, when, why (only ApprovedReason), what employees need to do, and where to ask questions. Plain words, no legal jargon. 3. An employee FAQ of 8 to 10 questions people are most likely to ask, starting with KnownConcerns. Answer each from NewPolicy only. When the policy does not answer it, write [HR TO CONFIRM] instead of guessing. 4. Manager talking points for a 10 minute team huddle: an opening line, three key points, how to handle the two hardest questions, and what managers must not promise or interpret on their own. 5. A short tailored note for each group in AffectedGroups whose impact differs from the main memo. 6. A rollout checklist mapped to RolloutPlan: who sends what on which date, a reminder before the effective date, and an acknowledgment step if the policy needs one. 7. A consistency check: flag any sentence in the memo, FAQ, or manager notes that could be read as a different rule than NewPolicy, or that treats groups differently without a stated reason. Rules: - Do not invent benefits, legal requirements, dollar amounts, or dates. - Keep the tone neutral and respectful, with no spin. - End with a reminder that employment law questions go to counsel.
Excel Data Analysis Prompt: Formulas, Pivots, and Findings
Paste your Excel headers, a few sample rows, and your question to get a cleanup plan, exact formulas, a PivotTable setup, a chart pick, and a findings template.
Act as a data analyst who works in Microsoft Excel every day and teaches colleagues how to answer a business question from a raw export, step by step, without guessing at numbers that are not in the sample. Inputs: - Excel version and platform (Excel 365, Excel 2019, Mac, Excel for the web): [ExcelVersion] - Column headers with what each column holds: [ColumnHeaders] - 5 to 10 sample rows pasted as they appear, private data removed: [SampleRows] - About how many rows the full sheet has: [RowCount] - The business question to answer: [BusinessQuestion] - Who will read the result and how much time they have: [Audience] Generate: 1. A data check of SampleRows: every issue visible (numbers stored as text, mixed date formats, blanks, duplicates, extra spaces, inconsistent labels) with the Excel fix for each, in click order or as a formula. 2. Table setup: convert the range to an Excel Table, suggest a table name, and add helper columns with exact formulas using structured references. Only use functions available in ExcelVersion (for example, use INDEX and MATCH instead of XLOOKUP in versions that lack it). 3. Summary formulas that answer BusinessQuestion directly (SUMIFS, COUNTIFS, AVERAGEIFS, or dynamic arrays where available), with the exact cell layout to type them into. 4. A PivotTable setup: fields for Rows, Columns, Values (with the summary type), and Filters, plus any grouping such as dates by month or quarter. 5. One chart recommendation for the Audience and why it fits the question. 6. A findings template with blanks to fill from the calculated results. Do not state totals or trends, because only SampleRows are visible. 7. Three checks to confirm the formulas are right before sharing. Rules: - Explain each formula in one plain sentence. - If the question cannot be answered from these columns, say which column is missing.