Productivity
239 prompts in this category · Page 19 of 20
Make.com Scenario Outline from a Trigger and Action List
Outline a Make.com scenario from pasted triggers and actions. No invented apps, webhooks, or mappings.
Act as a Make.com architect outlining a scenario from a trigger and action list. You outline a Make.com (formerly Integromat) scenario from modules the user already has. You do not invent an app, a webhook URL, or a field mapping. This is not n8n, not Zapier, not Jira automation, and not a GitHub Action. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Make.com plan and region I use: [Plan] - Trigger module I already connected: [Trigger] - Action modules I already connected, in order: [Actions] - Field mappings I can prove (source -> target): [Map] - Filters and routers I allow (or NONE): [Filters] - Error handler I allow (or NONE): [Errors] - Webhook URL I may print (or NONE): [Hook] - What I must never call: [Never] - Words I must not use: [Banned] - Scheduling I can prove (or NONE): [Schedule] Generate: 1. Honesty ledger: plan, trigger, every action app, mappings, hook, schedule. Forbidden: apps and URLs not listed. 2. Module chain: Trigger then Actions in order. Number them. Do not insert a router unless Filters names one. 3. Mapping table: only Map rows. Missing fields write NOT IN INPUTS rather than guessing. 4. Filters: only Filters. If NONE, linear chain. 5. Errors: only Errors. If NONE, default scenario-level halt, do not invent a Slack alert. 6. Hook: only Hook. If NONE, no webhook URL. 7. Schedule: only Schedule. If NONE and Trigger is not polling, write schedule not specified. 8. Compliance pass: quote Banned words, n8n nodes, invented apps. Cut them. Constraints: - Make.com scenario outline only. Not n8n, Zapier, Jira automation, or GitHub Actions. - Never invent an app, webhook, or mapping. - Do not add modules that are not in Trigger or Actions. - If Hook is NONE, do not mint a URL. - No emojis.
ClickUp Hierarchy and Custom Fields from a Workflow
Turn a workflow description into a ClickUp space, folder, list, and custom-field map. No invented statuses, users, or automations.
Act as a ClickUp admin writing a hierarchy and custom-field map from a workflow. You write a ClickUp (2026) space / folder / list hierarchy plus custom fields from a workflow the user describes. You do not invent member emails, status names, or automations that are not in Inputs. This is not a Notion database, not Airtable, not Jira, and not Linear. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workspace and Space name I own: [Workspace] - Workflow stages I actually use: [Stages] - Lists I want (one job type per list): [Lists] - Custom fields I can prove (type + name): [Fields] - Members I may assign (emails as pasted): [Members] - Statuses per list I can prove: [Statuses] - Automations I allow (or NONE): [Autos] - What must never be a field: [Never] - Words I must not use: [Banned] - Sprint or points I use (or NONE): [Sprint] Generate: 1. Honesty ledger: workspace, stages, lists, fields, members, statuses, autos. Forbidden: users and fields not listed. 2. Tree: Space -> folders if Inputs grouped them -> lists from Lists. Do not add a folder the brief did not name. 3. Status map: each list gets only Statuses. Do not copy Scrum defaults if Statuses is a custom set. 4. Field table: name, type, which list. Types only from Fields. Never-list stays out. 5. People: assign only Members emails. If a list has no member, leave unassigned. 6. Autos: only Autos. If NONE, write no ClickUp automations in this pack. 7. Sprint: only Sprint. If NONE, omit points and sprints. 8. Compliance pass: quote Banned words, Notion properties, invented emails. Cut them. Constraints: - ClickUp hierarchy and fields only. Not Notion, Airtable, Jira, or Linear. - Never invent a member, status, or custom field. - If Autos is NONE, do not add automations. - If Sprint is NONE, do not add sprint points. - No emojis.
Calendly Event-Type Copy from a Role and Duration List
Write Calendly event-type names, descriptions, and invitee questions from a role and duration list. No invented availability or prices.
Act as a Calendly admin writing event-type copy from a role and duration list. You write Calendly event-type titles, descriptions, durations, and invitee questions from Inputs. You do not invent availability windows, Zoom links, prices, or buffer times that are not pasted. This is not a Google Calendar appointment schedule and not a Cal.com dump unless Inputs say so. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Host role and display name: [Host] - Event types I want (name intent + duration minutes): [Types] - Location options I can prove (phone, Google Meet, in person address): [Location] - Buffers and min-notice I can prove: [Buffers or NONE] - Invitee questions I must ask: [Questions] - What I never book on these types: [Never] - Tone and reading level: [Tone] - Words I must not use: [Banned] - Character notes (Calendly name length I will honor): [Limits] - Timezone to print on the page: [Zone] Generate: 1. Honesty ledger: host, durations, locations, buffers, questions. Forbidden: prices, availability hours, Zoom if Location has no Zoom. 2. Event table: one row per Types. Name, duration, location from Location only, buffer from Buffers or NOT IN INPUTS. 3. Public description (80-150 words) per type. No invented slots. Print timezone Zone as display text only. 4. Invitee questions: from Questions. Mark required vs optional only if Inputs say. Do not add a company-size question that was not listed. 5. Never book: quote Never in the description so invitees see it. 6. Internal naming: slug-like names without spaces if Limits asks, else human titles. 7. Missing availability: write a line that hours are set in Calendly availability, not in this copy. 8. Compliance pass: quote Banned words, invented prices, fake Zoom. Cut them. Constraints: - Calendly event-type copy. Not Google Appointment Schedule. Not Cal.com unless named. - Never invent availability, prices, or meeting URLs. - Durations only from Types. - If Buffers is NONE, do not invent 15-minute buffers. - No emojis unless Tone uses them.
Jira Automation Rule Pack from a Workflow Description
Turn a workflow description into Jira Cloud automation rules. No invented project keys, smart values, or Slack webhooks.
Act as a Jira Cloud admin writing automation rules from a workflow description. You write Jira Cloud automation (2026 rule builder) from a workflow the user describes. You do not invent project keys, custom fields, Slack webhooks, or smart values that are not in Inputs. This is not a Linear template and not a GitHub Actions workflow. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Jira Cloud site and project key: [Project] - Issue types and workflow statuses I actually have: [Workflow] - Triggers I want (issue created, field changed, scheduled): [Triggers] - Conditions and fields I can prove exist: [Fields] - Actions I allow (transition, comment, assign, email): [Actions] - Actors I may assign (account IDs or names as in Jira): [Actors] - Notifications (email only unless a webhook URL is pasted): [Notify] - What must never auto-transition: [Never] - How many rules: [Count or 4] - Words I must not use: [Banned] Generate: 1. Honesty ledger: project key, statuses, fields, actors, notify URLs. Forbidden: Slack unless a URL is pasted, custom fields not in Fields. 2. Rule list: Count rules. Each has name, trigger from Triggers, condition from Fields, action from Actions. 3. Smart values: only fields in Fields. If a smart value is unknown, write NOT IN INPUTS rather than {{issue.madeUp}}. 4. Transition table: from-status to-status only if both exist in Workflow. Honor Never. 5. Notify: email from Notify. Webhook only with a pasted URL. No invented Slack channel. 6. Scope: project Project only. Do not enable global automation unless Inputs say so. 7. Test cases: 5 issues that should and must-not fire, using Workflow names. 8. Compliance pass: quote Banned words, Linear fields, invented webhooks. Cut them. Constraints: - Jira Cloud automation only. Not Linear, not GitHub Actions, not Jira Data Center XML unless Inputs say DC. - Never invent a project key, custom field, or webhook. - Do not auto-transition statuses in Never. - No Slack without a pasted webhook URL. - No emojis.
Todoist Filter and Label Scheme from a Role Description
Design a Todoist filter and label scheme from a role description. No invented projects, karma scores, or tasks the role did not imply.
Act as a productivity coach designing Todoist (v889 / 2026 app) filters and labels for one role. You design labels, filters, and a small project list from a role description. You do not invent tasks, karma scores, or collaborators who are not in Inputs. This is not Notion and not Outlook rules. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Role title and company type: [Role] - Work hours and timezone: [Hours] - Projects I already have (or NONE): [Projects] - Priorities I actually use (p1-p4): [Priorities] - People I may mention: [People] - Tools I live in: [Tools] - Energy or context labels I want: [Contexts] - Words I must not use: [Banned] - How many filters max: [FilterCap] - What I refuse to track: [Refuse] Generate: 1. Tool lock: Todoist 2026. Filter query syntax only. Not Notion. Not Outlook. 2. Project list: only Projects. If NONE, propose at most 3 names clearly marked PROPOSED, not existing. 3. Label taxonomy from Contexts, People, and Tools. No label for Refuse items. 4. Filter queries (count <= FilterCap) with Todoist query syntax. Explain each in one line. 5. Today vs upcoming vs waiting. Hours and timezone from Hours. 6. Priority policy from Priorities only. Do not invent a p0. 7. What not to put in Todoist: Refuse. 8. Compliance pass: quote Banned words, invented karma, and extra people. Cut them. Constraints: - Todoist filter syntax (2026). Do not emit Things 3 or OmniFocus syntax. - Never invent a karma score or completed-task count. - Do not add collaborators not in People. - Stay at or under FilterCap filters. - Do not generate a 30-task starter list unless Inputs asked for tasks (they did not).
Linear Issue and Project Template from a Bug Report
Turn a bug report into a Linear issue plus a project template. No invented teams, cycles, or severity scores.
Act as a product engineer writing Linear (linear.app 2026) issue and project templates. You convert a pasted bug report into Linear fields. You do not invent a team key, cycle, estimate, or severity that is not in Inputs. This is not Jira and not GitHub Issues. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Team key and workspace I may use: [Team] - Bug report paste: [Bug] - Severity scale we actually use: [Sev] - Project name if this is a project, or NONE: [Project] - Labels I may apply: [Labels] - Repro environment I can prove: [Env] - Assignee I may name (or UNASSIGNED): [Assignee] - Cycle or none: [Cycle] - Words I must not use: [Banned] - Estimate scale I may use (or NONE): [Estimate] Generate: 1. Tool lock: Linear 2026. Not Jira. Not GitHub Issues. 2. Honesty ledger: team, labels, severity values, cycle, estimate, assignee, env facts from Inputs and Bug. 3. Issue title (60 chars) from Bug. Print count. No panic words from Banned. 4. Issue body: summary, repro from Env, expected vs actual from Bug, missing facts as NOT IN INPUTS. 5. Fields: team key, labels (only Labels), severity only if it matches Sev, assignee or UNASSIGNED, cycle or none. 6. Project template: if Project is NONE, skip. Else milestones that Bug actually implies, no extra epics. 7. Acceptance criteria: testable lines from Bug only. 8. Compliance pass: quote Banned, invented story points, and fake customers. Cut them. Constraints: - Linear field names. Do not emit Jira YAML. - Never invent a team, cycle, or estimate. - If Sev does not include a value, do not set priority. - Do not add screenshots you were not given. - No PII beyond what Bug already contains. Do not expand names.
Outlook Inbox Rules for One Role
Inbox rules for one role; match folders named in Inputs.
Act as an executive assistant designing Outlook rules. Inbox rules for one role; match folders named in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow / role: [Workflow] - Tools: [Tools] - Fields I actually have: [Fields] - Cadence: [Cadence] - Pain today: [Pain] - Do not automate: [DoNot] Generate: 1. Schema or rule map. 2. Configurable artifact (tables, formulas, templates, rules). 3. Sample row / example without fake PII. 4. Maintenance cadence. 5. Gaps. Constraints: - No em dashes. - Never invent stats, citations, social proof, DOIs, or IDs. - If Inputs are thin, list gaps instead of filling. - Version-lock named tools; else write unknown. - De-identify and add not-advice for legal, clinical, insurance, HR, veterinary, or education-plan content. - Stay on brief for: Outlook Inbox Rules for One Role
Job-Search Weekly Pipeline Board
Weekly pipeline board; no invented recruiter names.
Act as a career coach building a job-search board. Weekly pipeline board; no invented recruiter names. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow / role: [Workflow] - Tools: [Tools] - Fields I actually have: [Fields] - Cadence: [Cadence] - Pain today: [Pain] - Do not automate: [DoNot] Generate: 1. Schema or rule map. 2. Configurable artifact (tables, formulas, templates, rules). 3. Sample row / example without fake PII. 4. Maintenance cadence. 5. Gaps. Constraints: - No em dashes. - Never invent stats, citations, social proof, DOIs, or IDs. - If Inputs are thin, list gaps instead of filling. - Version-lock named tools; else write unknown. - De-identify and add not-advice for legal, clinical, insurance, HR, veterinary, or education-plan content. - Stay on brief for: Job-Search Weekly Pipeline Board
Obsidian Daily Note and Periodic Review Templates
Daily and periodic templates; no invented plugin APIs.
Act as an Obsidian power user. Daily and periodic templates; no invented plugin APIs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow / role: [Workflow] - Tools: [Tools] - Fields I actually have: [Fields] - Cadence: [Cadence] - Pain today: [Pain] - Do not automate: [DoNot] Generate: 1. Schema or rule map. 2. Configurable artifact (tables, formulas, templates, rules). 3. Sample row / example without fake PII. 4. Maintenance cadence. 5. Gaps. Constraints: - No em dashes. - Never invent stats, citations, social proof, DOIs, or IDs. - If Inputs are thin, list gaps instead of filling. - Version-lock named tools; else write unknown. - De-identify and add not-advice for legal, clinical, insurance, HR, veterinary, or education-plan content. - Stay on brief for: Obsidian Daily Note and Periodic Review Templates
Google Sheets QUERY from a Plain-English Question
QUERY from a plain-English question; match stated headers only.
Act as a Sheets analyst writing QUERY formulas. QUERY from a plain-English question; match stated headers only. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow / role: [Workflow] - Tools: [Tools] - Fields I actually have: [Fields] - Cadence: [Cadence] - Pain today: [Pain] - Do not automate: [DoNot] Generate: 1. Schema or rule map. 2. Configurable artifact (tables, formulas, templates, rules). 3. Sample row / example without fake PII. 4. Maintenance cadence. 5. Gaps. Constraints: - No em dashes. - Never invent stats, citations, social proof, DOIs, or IDs. - If Inputs are thin, list gaps instead of filling. - Version-lock named tools; else write unknown. - De-identify and add not-advice for legal, clinical, insurance, HR, veterinary, or education-plan content. - Stay on brief for: Google Sheets QUERY from a Plain-English Question
Airtable Base Schema from a Workflow
Base schema from workflow; no invented automations beyond Inputs.
Act as an Airtable architect. Base schema from workflow; no invented automations beyond Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow / role: [Workflow] - Tools: [Tools] - Fields I actually have: [Fields] - Cadence: [Cadence] - Pain today: [Pain] - Do not automate: [DoNot] Generate: 1. Schema or rule map. 2. Configurable artifact (tables, formulas, templates, rules). 3. Sample row / example without fake PII. 4. Maintenance cadence. 5. Gaps. Constraints: - No em dashes. - Never invent stats, citations, social proof, DOIs, or IDs. - If Inputs are thin, list gaps instead of filling. - Version-lock named tools; else write unknown. - De-identify and add not-advice for legal, clinical, insurance, HR, veterinary, or education-plan content. - Stay on brief for: Airtable Base Schema from a Workflow
Personal CRM Follow-Up Cadence from a Contact List
Turn a contact list into a personal CRM follow-up cadence with buckets, next touches, and no fake intimacy.
Act as a personal CRM coach. Build a follow-up cadence from a contact list. Do not invent last-meeting notes, family details, or gifts. This is not a weekly review and not a cold-email campaign. Inputs: - Contacts (paste): [Name, context, last real touch if known, goal] - Time I will actually spend: [Minutes per week] - Channels I use: [Email, text, LinkedIn, in person] - What I will not do: [No fake birthdays, no scraping, etc.] - Tool: [Notion / spreadsheet / paper] Generate: 1. Buckets: 3-5 (active deal, weak tie, care, pause). Rules for each. If last touch is unknown, bucket = NEED DATE, do not guess a friendship. 2. Cadence table: bucket, frequency, channel, max minutes. 3. This week's list: only as many names as Time allows. Next touch in one line, using only pasted context. 4. Script stubs (3 types): check-in, ask, close-the-loop. No fake "great seeing your kid". 5. Stop rules: when to pause a person. No guilt language. 6. Tool mapping: columns for the Tool. No invented CRM prices. Constraints: - Do not scrape LinkedIn. Do not invent a spouse name. - Distinct from a partnership cold sequence and from a winback campaign.