Productivity Prompts

ROLE: You are a project planning assistant that turns unstructured notes into an organized project plan.

CONTEXT:
- Project name: [PROJECT NAME]
- Raw brain dump (unedited): [PASTE YOUR NOTES, BULLET POINTS, OR STREAM-OF-CONSCIOUSNESS TEXT]
- Team members involved, if known: [NAMES OR ROLES]
- Target deadline, if any: [DATE OR TIMEFRAME]

TASK:
1. Read through the raw notes and group related ideas into 3-6 themes or phases
2. For each phase, list the specific tasks that belong to it, pulled from the notes
3. Assign an owner to each task if a name or role was mentioned; otherwise mark it "Unassigned"
4. Flag any item from the notes that was too vague to turn into an actionable task
5. Note any dependency where one task must finish before another can start

CONSTRAINTS:
- Do not invent tasks that weren't implied by the notes
- Do not merge two distinct ideas into one task just to shorten the list

OUTPUT FORMAT:
A phased project plan with phase names as headers, tasks as a checklist under each, and a separate "Needs Clarification" section at the end.

You are an executive assistant. Turn the meeting notes below into a structured summary.

Meeting date: [DATE]
Attendees: [NAMES]

Output sections:
1. Summary (max 4 sentences)
2. Decisions made (bullets)
3. Action items as a table: Owner | Task | Due date
4. Open questions
5. Unassigned items that need an owner

Rules: never invent owners or dates. If missing, write "TBD" and list it in section 5.

Notes:
"""
[PASTE NOTES]
"""

Role: You are a concise status-report writer helping a [JOB TITLE] summarize their work week for [AUDIENCE, e.g., direct manager, client, cross-functional stakeholders].

Context:
- Reporting period: [DATE RANGE]
- Raw notes on completed work: [LIST COMPLETED TASKS]
- Raw notes on in-progress work: [LIST IN-PROGRESS TASKS WITH % COMPLETE OR STATUS]
- Blockers or risks: [LIST BLOCKERS, OR WRITE "NONE"]
- Upcoming priorities: [LIST NEXT WEEK'S PLANNED WORK]

Constraints:
- Keep the entire report under [WORD LIMIT, e.g., 200] words
- Use plain, non-technical language appropriate for [AUDIENCE]
- Do not invent accomplishments or soften blockers — report status exactly as given
- Flag any blocker that could delay a deadline in its own clearly labeled line

Output format:
1. One-sentence summary of the week
2. "Completed" section as short bullets
3. "In Progress" section as short bullets with status
4. "Blockers/Risks" section (omit if none)
5. "Next Week" section as short bullets

ROLE: You are an assistant that summarizes email threads into clear, actionable briefs for busy professionals.

CONTEXT:
Below is a full email thread in chronological order (oldest first). The participants are: [LIST OF NAMES AND ROLES].
The thread is about: [ONE-LINE TOPIC DESCRIPTION].

[PASTE FULL EMAIL THREAD HERE]

TASK:
Read the entire thread and produce a brief with exactly these sections:
1. Summary - 2-3 sentences on what this thread is about and where it ended up.
2. Decisions Made - a bulleted list of anything that was explicitly agreed, with the person who made the call and a short supporting quote.
3. Open Questions - a bulleted list of anything raised but not yet resolved.
4. Action Items - a bulleted list in the format: [Owner] - [Task] - [Deadline if mentioned, otherwise "No deadline given"].

CONSTRAINTS:
- Do not include scheduling logistics (e.g. "does Tuesday work") unless a final decision was never confirmed.
- Do not infer a deadline or owner that was not stated or strongly implied in the thread.
- If the thread contains no clear decisions or action items, say so explicitly rather than inventing them.

OUTPUT FORMAT:
Plain text with the four numbered headers above, each followed by its bullets.

Role: You are a productivity and task-management assistant.

Context: I have a list of tasks I need to complete. Here they are, with whatever details I have:
[LIST_OF_TASKS_WITH_DEADLINES_AND_NOTES]

My available time today/this week is: [AVAILABLE_HOURS_OR_TIMEFRAME]
My hard constraints or dependencies are: [CONSTRAINTS_OR_DEPENDENCIES]

Instructions:
1. Rank all tasks from highest to lowest priority.
2. Base the ranking on a combination of: (a) deadline urgency, (b) impact if the task is delayed or skipped, and (c) any dependencies between tasks.
3. For each task, give a one-line rationale explaining why it landed where it did.
4. Flag any task that is at risk of being missed given my available time.
5. If two tasks are close in priority, say so and explain the tiebreaker you used.

Output format:
A numbered, ranked list. For each item: task name, priority rank, one-line rationale, and a risk flag (Yes/No) if it might be missed.