Productivity
71 prompts in this category · Page 6 of 6
Decision-Forcing Meeting Agenda Writer
Build a meeting agenda that forces named decisions, owners, and a no-decision fallback, not a notes-to-actions converter.
Act as a chief of staff. Write an agenda that forces decisions. This is not a meeting-notes-to-action-items converter. You are planning the meeting before it happens. Inputs: - Meeting purpose: [Purpose] - Length: [Minutes] - Attendees and decision rights: [Who can decide what] - Decisions that must leave the room: [List] - Pre-reads that exist: [Docs or none] - What is out of scope: [Out] - Facilitation constraints: [Remote / in person, no slides, etc.] Generate: 1. Success = which named decisions are logged, not "alignment". 2. Timed agenda: minutes, topic, decision question (yes/no or pick A/B/C), owner of the decision, input-only people. 3. Pre-read: 5-line brief if Docs exist; if none, write NEED PRE-READ rather than a fake appendix. 4. Parking lot rule: what gets written down vs what gets decided today. 5. If we do not decide: the default that happens Monday (must be explicit). 6. Not this prompt: recap emails, OKR trees, note-taking templates. Constraints: - Every block has a decision question or it is cut. - Do not invent attendees who are not in Inputs. - Honor Length. Cut topics before shrinking them to 2 minutes of fake discussion.
SOP from Messy Notes with IF/THEN Branches
Turn messy notes or a transcript into an SOP with IF/THEN branches, a version header, and a first-time-user reading level.
Act as an operations writer. Turn messy notes into an SOP a first-time teammate can follow. Include IF/THEN for real branches. Do not invent systems, logins, or legal policies. Inputs: - Process name: [Name] - Messy notes or transcript: [Notes] - Who performs it: [Role] - Tools they actually have: [Tools] - Risks / if things go wrong: [Risks] - Version: [v0.1 date] - Reading level: [plain / regulated] Generate: 1. Header: title, owner Role, version, last updated, purpose, out of scope. 2. When to use / when not to use. 3. Numbered steps. One action each. Tools named only if in Inputs. 4. IF/THEN table: condition, action, who to ping. Only from Risks or Notes. If a branch is implied but unspecified, NEED OWNER. 5. Definition of done: 3 bullets. 6. Open questions: what the notes never said (passwords, SLAs). 7. Do not: invent a HIPAA policy, a refund percent, or a tool they do not have. Constraints: - First-time-user level. No unexplained acronyms. - Distinct from a weekly review or a meeting-notes extractor.
Excel Formula and VBA with Version and Sample Row
Write Excel formulas or VBA locked to 365 vs 2019, using a sample row, preferring formulas over macros when they suffice.
Act as an Excel specialist. Version-lock Microsoft 365 vs Excel 2019/2021. Prefer a formula. Use VBA only when the user needs a loop, file dialog, or event the formula cannot do. Always use their sample row. Inputs: - Excel version: [Microsoft 365 / Excel 2019 / Excel 2021 / Mac 365] - Sheet layout: [Columns, header row] - Sample row (paste): [Row] - Job: [Job] - Allowed: [Formula only / VBA OK / either] - Locale: [US comma / EU semicolon] Generate: 1. Version fork: functions that will fail on 2019 (TEXTSPLIT, FILTER, LAMBDA, XLOOKUP vs VLOOKUP). 2. Recommended formula on the sample row, with the result you expect. If you cannot compute, say NEED ROW. 3. 2019 fallback if they are on 2019 or if Allowed is formula only and 365 functions were used. 4. VBA only if needed: one Sub, Option Explicit, no ActiveSheet roulette if you can use a named sheet. Comment where it will not run on Mac if that is true. 5. Test steps: 3, including a blank cell and a type mismatch. 6. What I refused: volatile INDIRECT unless asked, sending a .xlsm when a formula works. Constraints: - Do not invent Power Query M unless asked. - Do not dump a whole payroll app. - Match Locale separators.
Notion Database Schema from a Workflow
Design a Notion database schema with properties, relations, formulas, and views from a messy workflow, without fake workspace IDs.
Act as a Notion architect. Turn a workflow into a database schema. Do not invent workspace IDs, credits, or sample customer PII. Inputs: - Workflow in messy notes: [Notes] - Who uses it: [Roles] - What must be unique: [Unique] - Views they asked for: [Views] - Formula comfort: [None / simple / rollups] - What not to automate: [Out] Generate: 1. Objects: 1-3 databases, purpose, why not one table. 2. Properties table: name, type, options, required. Relations named both ways. 3. Formulas / rollups: only if comfort allows. Paste-ready formula text using current Notion functions you are sure of; else describe and mark VERIFY in-app. 4. Views: each requested view with filters and sorts. No fake charts. 5. Permissions: who can edit vs view, in words (Notion plan unknown: do not invent enterprise flags). 6. Seed: 3 example rows with fake but non-PII names. 7. Out of scope: what stays in a doc, not a property. Constraints: - No made-up API tokens. - Do not dump a second-brain Zettelkasten unless asked. - Distinct from a weekly review prompt.
Habit System with If-Then Implementation Plans
Design a small habit system with if-then plans, stacking, environment cues, and a two-week experiment. No 30-habit overhaul.
Act as a behavioral design partner. Build a tiny system around 1-3 habits. Use implementation intentions (if-then), environment, and a review. Do not medicalize. Do not promise identity rebirth. Inputs: - Habits I want: [1-3, current baseline] - Why now: [Trigger] - When my days actually run: [Wake, work, meals, kids, commute] - Fail history: [Where this died before] - Environment: [Home, office, phone] - Constraints: [Health, travel, money, no-shame rule] - Tracking I will really do: [Paper / one checkbox / none] - Social: [Who notices] - Horizon: [Two weeks default] Generate: 1. Scope: Which habit is the keystone this cycle. Which one waits. 6-8 sentences. If all three are huge, cut to one. 2. If-then plans: For each kept habit, 2-3 implementation intentions: If [cue], then [tiny behavior]. Include a travel version and a bad-day version that is smaller, not zero, unless Constraints say rest is the plan. 3. Environment: 5 friction cuts (make it easier) and 3 friction adds (make the old pattern harder). No shopping spree. Use what is in Environment. 4. Stack: Attach to an existing stable habit from When my days actually run. Name the host habit. If none is stable, use a time+place cue instead and say it is weaker. 5. Two-week experiment: Success definition that is count-based, not mood-based. What we will not change mid-week. Midpoint check question. 6. Relapse rule: One missed day is data. Two-line restart script. No punishment work. 7. Tracking: The minimum checkbox. A weekly 5-minute review prompt. 8. Anti-goals: 4 things this system will not try (5am club, streak worship, public shaming). Constraints: - No em dashes. No "atomic" as a brand voice. No invented medical advice. - Tiny behaviors under 2 minutes for the bad-day version. - If Fail history names shame, do not add public streaks. - Write for a skeptical adult, not a morning-routine influencer.
Calendar Time-Block Planner for a Chaotic Week
Turn a chaotic week of meetings, travel, and tasks into realistic time blocks with buffers, travel, and protected deep work. No fantasy 5am schedule.
Act as a calendar surgeon. Fit work into the week that already exists. Do not delete immovable meetings. Do not invent 5am magic. Name what will slip. Inputs: - Time zone and work hours: [TZ, earliest start, latest stop] - Week: [Dates] - Immovable: [Meetings, school, travel, care] - Tasks that need time: [List with rough minutes] - Deep work I want: [Project names] - Energy pattern: [Mornings / afternoons / known bad days] - Constraints: [Commute, lunch, no-meeting blocks I already own] - Tools: [Google / Outlook / paper] - What I am willing to drop: [List] - Sleep and personal: [Non-negotiables] Generate: 1. Load check: Sum of task minutes + meeting hours vs available hours. A sentence on whether this week is already over. What slips first from What I am willing to drop. 2. Principles for this week only: 5 rules (buffer, travel, meal, shutdown, one deep-work window). 3. Day-by-day blocks: For each day, a table-like list: start-end, label, type (immovable / deep / admin / buffer / personal / travel). Include 10-15 min buffers after hard meetings. Put Deep work I want in Energy pattern hours if those hours are free. 4. Travel and logistics: Door-to-door, not just the meeting start. 5. Task-to-block map: Every task from Inputs either sits in a block or is explicitly deferred with a date. 6. Overflow: A parking lot with the first day it can live. 7. Calendar paste: A plain list I can type into Tools, one line per block: Day, start-end, title. 8. Failure modes: If a meeting overruns 30 min, what gets eaten. A Thursday 4pm re-plan rule. Constraints: - If hours do not fit, cut. Do not shrink lunch to 5 minutes. - No em dashes. No 4am workout unless Inputs asked. - Honor Sleep and personal as immovable. - Do not add tasks I did not list. - Write times in the user's time zone, 24h or am/pm consistently.
Second-Brain Note from a Raw Brain Dump
Turn a messy voice dump or notes pile into a durable second-brain note: claim, sources, links, next actions, and a filename you can find later.
Act as a knowledge manager who uses a second brain to think, not to hoard. Distill a dump into one durable note. Do not invent quotes, citations, or tasks. If the dump is several notes, say so and split. Inputs: - Dump: [Paste raw notes, transcript, or bullets] - Destination system: [Obsidian / Notion / Apple Notes / paper] - Note type I want: [Literature / project / person / fleeting-to-permanent] - Existing vault context: [Related note titles I already have, or none] - Link style: [Wiki-links / URLs / none] - How I will use this: [Write, decide, reuse in 6 months] - Tags I already use: [List or none] - Hard split: [If this should be more than one note, say the max] Generate: 1. Diagnosis: Is this one note or several? What is the atomic claim. What is noise. 6-8 sentences. 2. Title and filename: Human title. Machine filename (date optional). A 1-line description for search. 3. Permanent note: - Claim (2-4 sentences) - Why it matters to me (from How I will use this) - Evidence from the dump only, quoted short - Open questions - Next actions (only if they are in the dump or are mechanical filing) 4. Links: 5 suggested links to Existing vault context, or "create these 3 stubs" if none. No fake titles presented as if they already exist. 5. YAML or properties: tags (max 5, prefer my existing), created date placeholder, type. 6. Fleeting leftovers: bullets that should NOT go in the permanent note (errands, venting). 7. Split plan: If you recommended multiple notes, a table: filename, claim, where the dump lines went. Constraints: - Quote the dump when you claim it said something. No fake authors. - No em dashes. No PARA lecture. One good note beats a taxonomy sermon. - Do not turn this into a daily journal unless Note type says so. - If Dump is empty, stop. - Write so 6-months-later me can understand without the dump.
Weighted Decision Matrix for a Messy Choice
Build a transparent weighted decision matrix for a messy personal or work choice, including scores, sensitivity, and a gut-check so the numbers do not fake certainty.
Act as a decision coach who uses numbers as a flashlight, not as a verdict. Build a matrix. Then try to break it. Do not invent options or criteria the user did not imply. Inputs: - Decision: [The choice in one sentence] - Options: [2-6 real options; include "do nothing" if it is real] - Must-haves: [Hard constraints that kill an option] - Criteria I care about: [List, even messy] - Weights if I have them: [Or "help me weight"] - Facts I know: [Numbers, dates, quotes from people] - Unknowns: [What I still need] - Who is affected: [People] - Deadline: [Date] - Risk I will regret: [Wrong kind of error] Generate: 1. Frame: Restate the decision so it is not two decisions glued together. If it is, split and say which matrix this is. 2. Kill list: Any option that fails a must-have. One sentence why. Survivors only go to scoring. 3. Criteria: 5-8. Each: definition, how 1 vs 5 would look, data source (Facts vs judgment). Merge duplicates. Ban vague "culture" unless defined. 4. Weights: 100 points. If Inputs had none, propose weights and mark them as yours. One sentence on what you over-weighted given Risk I will regret. 5. Matrix: Option x criterion. Score 1-5. Show weighted total. A note under any score that is a guess. 6. Sensitivity: Which two weights, if flipped, would change the winner. A one-row "if I am wrong about X" test. 7. Gut check: What the scores ignore (identity, timing, fatigue). A 10-minute experiment that would change a score before Deadline. 8. Recommendation: Winner, first action in 48 hours, what would make you reopen. If totals are within 5 points, say it is a tie and use the experiment, not a fake precision ranking. Constraints: - No em dashes. No fake research citations. - Do not add a surprise option unless labeled as optional extra and not scored as if the user asked for it. - If Facts I know are thin, more scores must be marked GUESS. - Write for someone who will show this to a spouse or a boss.
Weekly Review and Next-Week Plan Generator
Turn a messy week of notes into a GTD-style weekly review, a next-week plan with three priorities, and a shutdown checklist you can run in 30 minutes.
Act as an operations coach who has run weekly reviews with founders and ICs. Close last week. Open next week. Do not invent meetings, tasks, or feelings that were not in Inputs. Prefer fewer commitments. Inputs: - Role and hours: [Job, typical hours, time zone] - Week just ended: [Dates] - Wins: [Done work, even small] - Open loops: [Tasks, waiting-on, worries] - Calendar residue: [Meetings that overran, holes] - Energy and health: [Sleep, focus, constraints] - Personal non-work: [Family, errands, rest] - Next week hard landscape: [Fixed meetings, travel, deadlines] - Capacity: [Deep-work hours I actually have] - Tools: [Calendar, task app] - Goal of the review: [Calm / catch-up / ambitious] Generate: 1. Closeout: 8-10 sentences. What actually moved. What was theater. One sentence on energy, labeled as inference if Inputs are thin. 2. Inbox zero for the mind: Sort Open loops into Done / Do next week / Waiting on (name a person) / Someday / Delete. No item left unsorted. 3. Three priorities for next week: Outcome language, not a 20-line to-do. Each: done-when test, first physical next action, a time block suggestion, what you will say no to so it fits. 4. Next-week plan: Day-by-day from the hard landscape. Put deep work where Capacity lives. Protect one recovery block. Flag any day that is already over capacity and cut. 5. Waiting-on list: Person, ask, date you will nudge. Scripts of 2 sentences max. 6. Metrics I will not track: 4 vanity measures to ignore this week. 7. 30-minute run sheet: Minute-by-minute so I can do this again next Friday without you. 8. Shutdown phrase: One line I can say when the week is closed. Constraints: - If Capacity is missing, assume 10 deep-work hours and say so. - Do not add habits I did not ask for. Do not invent a 5am routine. - No em dashes. No "crush it." No 40-item task dump. - Honor health constraints. If energy is low, cut the plan, do not pep-talk. - Write for a tired person on Friday at 4pm.
Professional Email Rewriter: Tone, Length & Outcome
Rewrite any email for a target outcome. Get 3 tone variants, a shorter version, and a subject line set that actually gets opened.
Act as an executive communications editor. Rewrite the draft so it gets the Outcome. Keep every factual claim that is in the draft. Cut hedges, throat-clearing, and fake warmth. Inputs: - Draft: [Paste the email or message] - Recipient: [Role, relationship, how they like to communicate if known] - Outcome: [The one thing that should happen next] - Constraints: [Things I must not say, legal, cc politics, or "none"] - Max length: [Word cap for the recommended send] - Channel: [Email / Slack / both] Generate: 1. Diagnosis (short): What the draft is doing wrong (hedges, buried ask, tone mismatch, too many asks). What fact must be preserved. The actual ask in one line. Risk of the current draft. 2. Recommended send: The version you would actually ship. Within [Max length]. Subject line included if Channel is email. Match Recipient. One ask. Next step and date if the draft has one. If the draft has multiple asks, keep the one that serves Outcome and park the rest in a "not in this send" note. 3. Tone variants (3), same facts: - Direct: Short, verb-led, no softening. - Warm: Human but still clear. No "just circling back" or "hope you're well" unless Recipient truly requires it. - Formal: Complete sentences, titles if appropriate, still no pomp. After each, one line: when to use this variant. 4. Shorter version: Half the word count of the recommended send, or 50 words, whichever is smaller. Still contains the ask and any deadline. 5. Subject lines (5): Each under 46 characters including spaces. Mix: specific + date, outcome-led, question, document name, light tension. No "Quick question," "Following up," or "Touching base." Mark the recommended one. 6. Slack / chat version: 2-6 lines. No subject. No sign-off. If Channel is email-only, still provide this as an option. 7. Follow-up (2 sentences): If they do not reply. Time gap suggestion. No guilt. Constraints: - Keep facts from the draft. Do not invent attachments, meetings, numbers, or promises that were not there. - Cut: "just," "I was wondering if," "circle back," "per my last email," "don't hesitate," "please don't hesitate to reach out," "I hope this email finds you well," exclamation piles, and apology for existing. - One Outcome. If the draft wants two things, say so in Diagnosis and pick one. - Do not change the meaning of a commitment or a date. - Tone is adult-to-adult. No flattery, no dominance games.
Meeting Notes to Action Items Converter with Follow-Ups
Transform raw meeting notes or transcripts into structured action items, decisions, key takeaways, and automated follow-up reminders.
Act as an executive assistant and project coordinator skilled at extracting actionable insights from unstructured meeting notes. I will provide raw meeting notes or a transcript. Process them into a structured output. Input: [Paste your meeting notes or transcript here] Meeting Context: Meeting Type: [Stand-up / Strategy / Client / Brainstorm / 1-on-1] Attendees: [List of participants] Date: [Meeting date] Generate: Meeting Summary: A 3-5 sentence executive summary of what was discussed and the overall outcome. Key Decisions Made: List each decision with: Decision statement Who made or approved it Any conditions or caveats Action Items Table: For each action item extract: Task description Owner (who is responsible) Deadline (stated or inferred) Priority (High / Medium / Low) Dependencies (if any) Open Questions: List any unresolved topics that need follow-up discussion. Parking Lot: Items mentioned but deferred to a future meeting. Follow-Up Email Draft: A professional email summarizing the meeting, listing action items, and confirming next steps. Ready to send to attendees. Next Meeting Agenda Suggestions: Based on open items and upcoming deadlines, suggest 3-5 topics for the next meeting. Constraints: If a deadline is not explicitly mentioned, flag it as 'TBD - needs confirmation'. Attribute action items to specific people. If unclear, mark as 'Unassigned'. Tone: Professional, concise, and action-oriented. Format: Use tables for action items and bullet points for everything else.