APromptAura

p/productivity

Notes to action items, triage, planning, and personal ops.

hotnewtopstill works
filter✓ verified in 30 dayshas example output
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Reverse-engineer a busy week backward from one non-negotiable event

I have one big non-negotiable event coming up: key_event on event_date. Everything else on my plate this week: other_commitments. Work backward from the event to build my week: 1. List everything that must be true or ready by the moment the event starts, be specific and concrete, not "be prepared." 2. For each readiness item, state how long it will actually take and the latest point in the week it could start and still finish in time, accounting for realistic buffer, not the minimum possible time. 3. Slot those prep tasks into specific days, working backward from the event, and show me the resulting day-by-day plan. 4. Take my other stated commitments and mark each one as: fits around the plan as-is, needs to move, or needs to be dropped this week given the priority of the event. 5. Flag the single riskiest day, the one where if something goes wrong, the whole plan is most likely to break.
ClaudeGPT#backward-planning#event-prep#scheduling
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Build a habit-formation plan anchored to an existing routine

I want to build this new habit: target_habit. Rather than generic advice, anchor it to my actual existing routine: existing_daily_routine. 1. Identify the single best existing routine moment to attach this new habit to (habit stacking), and explain specifically why that moment works better than the alternatives. 2. Shrink the habit down to a version so small it feels almost silly not to do (the two-minute version), and describe exactly what that looks like. 3. Define the specific trigger-action-reward loop: what exact cue starts it, what the minimal action is, and what immediate reward (not a long-term benefit, an immediate one) reinforces it. 4. Name the most likely day this habit breaks (which day of the week, based on my routine) and a specific recovery rule for getting back on track within 24 hours rather than letting one miss become a month-long lapse. 5. Suggest one visible tracking method that takes under 10 seconds to update.
ClaudeGPT#habit-formation#routine-design#behavior-change
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Draft a scope-creep pushback email that protects the relationship

A client/stakeholder is asking for additional work beyond what was originally agreed: original_scope was agreed, and now they're asking for new_request. I want to push back without damaging the relationship or sounding petty about it. Write an email that: acknowledges the request warmly and takes it seriously rather than sounding defensive, clearly restates the original scope so there's no ambiguity about what was agreed, explains the tradeoff plainly (this addition means either more time, more budget, or something else gets cut, name the specific tradeoff), offers 2 concrete paths forward (e.g. add it to a phase 2, or adjust the timeline/budget now), and closes by asking a specific question that moves the decision forward rather than leaving it open-ended. Tone: tone_preference. Keep it under 150 words.
ClaudeGPT#client-communication#scope-management#email-drafting
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Compare two job or project offers with a real weighted framework

I'm deciding between these options: option_a_description and option_b_description. My priorities, roughly ranked: ranked_priorities (e.g. compensation, growth, stability, autonomy, location). Build a weighted decision framework: 1. Turn my ranked priorities into weights that sum to 100, reflecting the ranking I gave (don't just split evenly). 2. Score each option 1-10 on each priority based only on what I've told you, and where I haven't given enough detail to score confidently, say so and ask rather than guessing. 3. Calculate the weighted total for each option and show the math, not just the final number. 4. Identify which single priority, if I'm wrong about its weight, would flip the recommendation, this tells me what to actually be sure about before deciding. 5. Give a final recommendation, but explicitly note if the scores are close enough that the framework shouldn't be the deciding factor and gut instinct matters more.
ClaudeGPT#decision-framework#job-offer#weighted-scoring
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Design a no-meeting focus day and defend it against the calendar

Help me carve out one real no-meeting focus day per week. My current calendar pattern: current_calendar_pattern, and the recurring meetings I'm attached to: recurring_meetings. My biggest deep-work project right now: deep_work_project. 1. Recommend which day of the week is the best candidate, reasoning from my actual pattern, not a generic "Wednesdays are best" answer. 2. For each recurring meeting currently sitting on that day, classify it as: move it, decline it, or it's truly unmovable, with a one-line justification for each. 3. Write me the exact short message I'd send to reschedule a recurring meeting, polite but firm, that I could paste directly. 4. Predict the single most likely way this focus day gets eroded within a month (a specific meeting type or habit, not a vague warning), and give me one concrete rule to prevent that specific erosion.
ClaudeGPT#calendar-management#focus-time#boundaries
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Batch-process a backlog of unread articles into a decision list

I have a backlog of saved articles/links I never got to, here are the titles and one-line summaries: article_backlog. My current priorities are: current_priorities. Sort the whole backlog into exactly four buckets: Read This Week (directly relevant to a current priority, genuinely worth the time), Skim Only (extract the key takeaway from the title/summary alone rather than reading in full, and write that takeaway for me), Archive for Reference (not urgent but might matter later, tag with a topic), and Delete (no longer relevant, say why). For every Skim Only item, actually write the 1-2 sentence takeaway you'd expect based on the summary given, so I get value without reading it. Be decisive, don't put more than 3 items in Read This Week or the exercise defeats its purpose.
ClaudeGPT#reading-backlog#information-management#triage
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Delegation brief that hands off a task without losing context

I need to delegate this task: task_description to delegate_name, who has this level of context already: their_existing_context. Write a delegation brief that actually transfers ownership, not just instructions. Include: the outcome I actually need (not the steps I'd take, the result), the boundary of their decision-making authority (what they can decide alone vs. what needs to come back to me), the 2-3 pieces of context I have that they probably don't, the deadline and why that deadline matters (so they can triage against other work), how and when I want a check-in (specific cadence, not "keep me posted"), and what "done" looks like in a single checkable sentence. Flag anything in the task description that sounds ambiguous enough that they'll need to ask me a clarifying question before starting.
ClaudeGPT#delegation#handoff#management
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Post-mortem writer that separates facts from blame

Help me write a blameless post-mortem for this incident: incident_description, which happened on incident_date and affected impact_description. Structure it as: 1. Timeline: a factual, timestamped sequence of what happened, no interpretation or blame language, just events (use placeholders like time if I haven't given exact times). 2. Impact: concrete, quantified where possible (users affected, revenue, downtime duration). 3. Root cause: the actual mechanical cause, not "human error", trace it back to the system or process gap that allowed the error to matter. 4. Contributing factors: 2-3 secondary conditions that made this worse or harder to catch, stated as system gaps, not individual failings. 5. What went well: at least 2 things that limited the damage or sped up recovery, credited specifically. 6. Action items: each one a specific system change with an owner and due date, ranked by how directly it prevents recurrence. Strip any language that assigns personal fault, even if I write it that way in my input.
ClaudeGPT#post-mortem#incident-review#process-improvement
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Convert a vague goal into a measurable OKR with honest scoring

I have a vague goal: vague_goal, for the time period time_period. Turn it into a proper OKR. 1. Rewrite it as a single Objective: inspiring, qualitative, one sentence. 2. Generate 3 Key Results that are genuinely measurable (a number, a date, or a binary yes/no), not disguised tasks. If I give you something that's actually a task pretending to be a KR, rewrite it and explain why. 3. For each Key Result, state the current baseline if I've given you one, or explicitly flag "baseline unknown, needs to be measured before this KR is valid." 4. Add one leading indicator per Key Result, something I could check weekly to know if I'm on pace, not just at the deadline. 5. Give me a simple scoring rubric (0.0 to 1.0) for each KR so grading it at the end isn't a debate. Context to work from: context.
ClaudeGPT#okr#goal-setting#measurement
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Meeting agenda that forces a decision instead of a discussion

I need to run a meeting about meeting_topic with attendee_list, scheduled for duration minutes. Build me an agenda designed to end in an actual decision, not just a discussion. For each agenda item, specify: the exact question that must be answered by the end of that segment (not a topic, a question), the time box in minutes, who needs to speak versus who is there to listen, and the pre-read or data each person should bring so the meeting isn't spent catching people up live. End the agenda with a mandatory "Decision and Owner" slot in the last 5 minutes where the specific decision gets restated and one person is named as owner of the next step. If the total time I have isn't enough for a real decision given the topic, tell me that directly instead of padding the agenda to fit.
ClaudeGPT#meeting-agenda#decision-making#facilitation
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Negotiation prep brief built from your actual constraints

Help me prepare for a negotiation: negotiation_context (e.g. salary, vendor contract, project scope). My actual constraints are: my_constraints (walk-away point, must-haves, nice-to-haves, timeline pressure). Build a prep brief with these sections: 1. My real interests vs. my stated position (what do I actually need underneath what I'm asking for). 2. Their likely interests, inferred from the context I gave you, flagged clearly as inference. 3. My best alternative if this negotiation fails (BATNA), stated honestly based on what I told you, not inflated. 4. Three opening moves ranked by how much they reveal vs. how much ground they hold. 5. Two likely objections they'll raise and a prepared response to each, grounded in my actual constraints, not generic scripts. 6. My walk-away trigger stated as a specific, checkable condition. Do not invent facts about the other party that I haven't given you.
ClaudeGPT#negotiation#preparation#decision-making
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Run a pre-launch readiness checklist audit against real evidence

I'm about to launch launch_description on launch_date. Instead of a generic checklist, interrogate my actual readiness. Ask me to answer these five categories one at a time, and for each answer, push back if my answer sounds like an assumption rather than verified evidence: 1. Technical readiness: what have you actually tested, versus what you assume works? 2. Communication readiness: who specifically has been told, and do you have proof they saw it (not just that you sent it)? 3. Rollback plan: if this goes wrong in the first hour, what is the exact step to undo it, and who can execute it? 4. Success definition: what specific number or signal, checked at what specific time, tells you this worked? 5. Owner on call: who is actually watching this in the first 24 hours, by name? After I answer all five, give me a go/no-go recommendation and name the single riskiest gap.
ClaudeGPT#launch-checklist#readiness-review#risk-assessment
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Convert a brain dump into a categorized, actionable second brain entry

I'm going to paste an unstructured brain dump, the kind of thing I type quickly into my phone with no organization: brain_dump_text. Process it into a clean second-brain entry: 1. Split it into distinct atomic ideas (one idea per line, don't merge unrelated thoughts). 2. Tag each idea with one category from this list: Task, Idea to explore later, Reference fact worth saving, Reminder, Question to research. 3. For anything tagged Task, rewrite it as a clear verb-first action. 4. For anything tagged Idea to explore later, add one clarifying follow-up question that would help me develop it further. 5. Group the final output under those five category headers, most actionable first. Don't lose any distinct thought from the original dump, even small ones, but do merge true duplicates.
ClaudeGPT#second-brain#note-taking#brain-dump
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Draft a difficult status update that names risk without spin

Help me write a status update for project_name that is going to stakeholders including audience_description. The honest situation is: honest_status (include what's on track, what's slipping, and why). Write the update following this structure: 1. One-sentence headline that states the real status, not a euphemism (green/yellow/red equivalent, but in plain words). 2. What's on track (brief, 2-3 bullets max, don't bury the real news under good news). 3. What's at risk and why, stated plainly with the actual cause, not passive-voice hedging. 4. What we're doing about it, with owners and dates. 5. What we need from the reader, if anything (decision, resource, patience). Tone should be tone_preference (e.g. calm and factual, or direct and urgent). Do not use corporate hedge phrases like "we are actively monitoring" without a concrete action attached. Keep the whole thing under 200 words.
ClaudeGPT#status-update#stakeholder-communication#risk-reporting
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Time audit analysis from a raw calendar or time-tracking export

I'm going to paste a raw export of my calendar or time-tracking log for the past time_period: raw_time_log. Analyze it as a time audit: 1. Bucket every entry into categories you infer from the titles (deep work, meetings, admin, communication, personal, unaccounted). State your inference logic briefly. 2. Calculate rough percentage of total tracked time per category. 3. Identify the three most fragmented parts of the week (lots of short gaps between commitments that prevent focus blocks). 4. Compare time spent against my stated priorities: stated_priorities, and call out the biggest mismatch between where time actually went and what I say matters most. 5. Recommend exactly 3 specific, actionable changes to the calendar structure for next week, not vague advice like "protect your time." Be blunt about the mismatch, don't soften it.
ClaudeGPT#time-audit#calendar-analysis#focus-time
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Prioritize a task list with an Eisenhower plus effort overlay

Here is my current task list, unsorted: task_list. Prioritize it using a combined framework: first classify each task by urgency (urgent/not urgent) and importance (important/not important) in the classic Eisenhower sense, then add a second dimension: estimated effort (quick under 30 min, medium under 2 hours, large half-day or more). Present the result as a table with columns: Task, Quadrant, Effort, Recommended Action (Do now, Schedule, Delegate, Drop). Then give me a suggested order for today assuming I have available_hours hours of real focus time, sequencing for momentum (a couple of quick wins early) while still protecting time for the single most important large task. Explicitly call out anything that looks like it should just be dropped or declined.
ClaudeGPT#prioritization#eisenhower-matrix#task-management
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Personal operating system setup: roles, systems, and weekly rhythm

Help me design a lightweight personal operating system for managing my life and work. My current situation: life_context (roles like parent, employee, side project founder, etc), and my biggest current friction is current_friction. Walk me through building this in four parts: 1. Roles: help me name 4-6 distinct roles I hold (not tasks, roles, like "team lead" or "household manager"). 2. Systems: for each role, suggest one lightweight system or habit that keeps it running without heroics (a weekly check-in, a specific list, a recurring time block). 3. Rhythm: propose a weekly rhythm (which days/times are for which role's deep work vs admin vs review), accounting for my actual constraints: schedule_constraints. 4. Guardrails: suggest 2-3 simple rules that prevent the system from decaying after two weeks, based on common reasons personal systems fail. Keep the whole thing simple enough that I could explain it to someone else in under two minutes.
ClaudeGPT#personal-systems#life-admin#habits
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Break a fuzzy project into a real plan with dependencies and risk

I have a fuzzy project idea, not yet a real plan: project_description. Target completion is roughly target_date, and my constraints are constraints (time, budget, team size, etc). Turn this into an actual project plan: 1. Restate the project as a single measurable outcome (not an activity). 2. Break it into 4-8 major milestones in logical sequence. 3. For each milestone, list the 2-4 concrete tasks underneath it, and flag any task that depends on another milestone finishing first. 4. Identify the single biggest risk to the timeline and one mitigation for it. 5. Identify what could be cut entirely if the timeline gets squeezed by 30%, and what absolutely cannot be cut. 6. Output a simple week-by-week schedule mapping milestones to calendar weeks from today. Be realistic about how long things actually take, don't just divide evenly. Call out if the target date looks unrealistic given the scope.
ClaudeGPT#project-planning#milestones#risk-management
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Decision memo generator using a pre-mortem and reversibility test

Help me write a one-page decision memo for the following choice: decision_description. Structure the memo exactly like this: 1. Decision statement: one sentence, unambiguous. 2. Options considered: list 2-4 real alternatives, including "do nothing." 3. Reversibility: is this a one-way or two-way door decision, and what would it cost to reverse it? 4. Pre-mortem: assume it's 6 months from now and this decision was a mistake, write 3 concrete reasons why it failed. 5. Recommendation: state the recommended option and the single strongest reason for it. 6. What would change my mind: name the specific piece of evidence that would make me reconsider. Use only the information I give you here: context_and_constraints. If information is missing to fill a section, say so explicitly rather than inventing it, and ask me a targeted question instead.
ClaudeGPT#decision-making#memo#pre-mortem
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Structured weekly review using the four-quadrant retrospective

Guide me through a structured weekly review. Ask me one question at a time, wait for my answer before moving to the next, and use this exact sequence: 1. What were my top 3 intended priorities this week (week_dates)? 2. For each, what actually happened: done, partially done, or not started, and why? 3. What consumed time that wasn't planned for, and was it worth it? 4. What is one thing I should stop doing, one thing I should start doing, and one thing I should keep doing next week? 5. Given all of the above, what are my top 3 priorities for next week, ranked? After I've answered all five, synthesize everything into a short written weekly review document with headers: Wins, Misses and Why, Time Leaks, Stop/Start/Keep, Next Week's Priorities. Keep it honest and specific, not generic corporate language.
ClaudeGPT#weekly-review#retrospective#reflection
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Inbox triage sweep that sorts, drafts, and flags in one pass

Act as my inbox triage assistant. I will paste a batch of email subject lines and short summaries below. Process the whole batch in one pass, applying this exact framework: - ARCHIVE: no action needed, purely informational, safe to archive - QUICK REPLY (under 2 minutes): draft a short reply I can send with light editing - SCHEDULE: needs a meeting or calendar action, note what needs to be booked - DEEP WORK: requires real thought or drafting later, add to a "handle this week" list - DELEGATE: someone else should own this, suggest who based on context clues Here is the batch: email_batch For every QUICK REPLY item, write the actual draft reply in my voice: tone_description. For every DELEGATE item, write a one-line forwarding note. Output grouped by category, most time-sensitive first within each group.
ClaudeGPT#inbox-management#email-triage#delegation
0
0
p/productivityAauraNovice4 days agohas example⁂auto-checked

Turn raw meeting notes into owned action items with due dates

You are an executive assistant converting messy meeting notes into a clean action item tracker. Here are my raw notes from the meeting titled "meeting_title" held on meeting_date: raw_notes Do the following: 1. Extract every commitment, decision, and open question, even if implied rather than stated outright. 2. For each action item, assign an owner (use the name mentioned, or write "UNASSIGNED" if unclear), a specific due date if one was mentioned or a reasonable inferred deadline if not (mark inferred dates with an asterisk), and a one-line description written as a clear next step, not a vague topic. 3. Separate items into three sections: Action Items, Decisions Made, and Open Questions Needing Follow-up. 4. Flag anything that sounds like a blocker or dependency on another team. 5. End with a 3-sentence summary suitable for pasting into a status update. Output as a markdown table for the action items and bullet lists for the rest.
ClaudeGPT#meeting-notes#action-items#delegation
0