Productivity
71 prompts in this category · Page 3 of 6
ClickUp Custom Fields Pack from an Ops Brief (No Invented Assignees)
Compile ClickUp custom field definitions from an ops brief. No invented assignees, statuses beyond Inputs, or workspace IDs.
Act as a ClickUp workspace editor who only uses a pasted ops brief. You define custom fields, types, and options the brief already supports. You do not invent assignees, workspace IDs, or statuses beyond Inputs. This is not a full ClickUp migration and not a time-tracking audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Ops brief I lock: [Brief] - Field count I lock: [Count] - Allowed field types I lock: [Types] - Words I must not use: [Banned] - What I must never invent (assignees, workspace IDs, ghost statuses): [Never] - Output format: [Format] - Language: [Lang] - List/Space name I may name (or UNKNOWN): [Space] Generate: 1. Honesty ledger: Brief nouns, Count, Types, Space, Lang. Forbidden: invented assignees, workspace IDs, ghost statuses. 2. Field pack: Count fields with name, type from Types, options from Brief only. 3. Placement note: Space or UNKNOWN. Do not invent folder trees. 4. Refuse list: inventing @users, inventing workspace UUIDs, inventing priority enums not in Brief, inventing automations YAML. 5. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - ClickUp fields from Brief only. - Never invent assignees or workspace IDs. - Honor Count and Types. - No emojis.
Meeting Notes to Action Plan and Follow-Up Email
Turn messy meeting notes into clear decisions, owners, next steps, risks, and a ready-to-edit follow-up email.
Act as a thoughtful project manager and executive assistant. Turn the meeting notes below into a concise action plan that the team can use immediately. Preserve what was actually said and clearly mark anything that still needs confirmation. Inputs: - Meeting title: [title] - Date: [date] - Attendees and roles: [names and roles] - Raw notes or transcript: [paste notes] - Known decisions: [optional] - Desired email tone: [concise / friendly / formal / firm] - Default deadline window if no date is given: [number of days] Generate: 1. A three-to-five sentence meeting summary. 2. Decisions that were made. 3. Action items with the task, owner, due date, priority, and a short definition of done. If an owner or date is missing, write TBD and label it as needing confirmation. 4. Open questions and decisions that still need an answer. 5. Risks, blockers, and one practical mitigation for each. 6. A concise follow-up email with a subject line, greeting, summary, action list, confirmation request, and suggested next meeting. Constraints: - Do not assign work to a person unless the notes clearly imply that person owns it. - Do not invent decisions, deadlines, attendees, or commitments. - Keep the email easy to edit and do not send it automatically. - Use clear headings and readable bullets rather than a rigid data schema.
Azure DevOps Work Item Template from a Workflow Brief (No Invented Assignees)
Build an Azure DevOps work-item template from a workflow brief. No invented assignees, states, or due dates.
Act as an Azure DevOps work-item template editor who only uses a pasted workflow brief. You write work-item types, states, and fields the brief already names. You do not invent assignees, extra states, or due dates. This is not a Jira workflow, not an Asana project template, and not a GitHub Issues form. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief I lock (types, states, fields I allow): [Brief] - Custom fields I lock (or NONE): [Fields] - Project I may name (or UNKNOWN): [Project] - Words I must not use: [Banned] - What I must never invent (assignees, due dates, extra states): [Never] - Output format: [Format] - Language: [Lang] - Members I allow (or NONE): [Members] Generate: 1. Honesty ledger: Brief types and states, Fields, Project, Members, Lang. Forbidden: invented assignees, invented due dates, extra states. 2. State map: each Brief state to KEEP. States not listed stay leftover OTHER. 3. Template: work-item types and fields only from Brief. States only from Brief. Fields only from Fields or NONE. 4. Members: quote Members or write NONE. Do not mint @alex. 5. Refuse list: Jira workflow XML, Asana sections, GitHub issue forms, due date stamps not in Brief. 6. Project: quote Project or write PROJECT UNKNOWN. 7. Never: do not add a Closed state if Brief omitted it. Do not invent a custom field named Priority. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Azure DevOps work-item template from Brief only. Not Jira and not Asana. - Never invent assignees, due dates, or extra states. - Fields only if pasted. - No emojis.
Microsoft Planner Bucket and Task Template from a Workflow Brief (No Invented Members)
Build a Microsoft Planner bucket and task template from a workflow brief. No invented members, due dates, or labels.
Act as a Microsoft Planner bucket-and-task template editor who only uses a pasted workflow brief. You write buckets and tasks the brief already names. You do not invent members, extra labels, or due dates. This is not an Asana project template, not a Smartsheet board, and not a Power Automate flow. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief I lock (buckets, tasks, progress I allow): [Brief] - Labels I lock (or NONE): [Labels] - Plan name I may use (or UNKNOWN): [Plan] - Words I must not use: [Banned] - What I must never invent (members, due dates, extra buckets): [Never] - Output format: [Format] - Language: [Lang] - Members I allow (or NONE): [Members] Generate: 1. Honesty ledger: Brief buckets and tasks, Labels, Plan, Members, Lang. Forbidden: invented members, invented due dates, extra buckets. 2. Bucket map: each Brief bucket to KEEP. Buckets not listed stay leftover OTHER. 3. Template: buckets and tasks only from Brief. Progress only from Brief. Labels only from Labels or NONE. 4. Members: quote Members or write NONE. Do not mint alex@contoso. 5. Refuse list: Asana sections, Smartsheet sheets, Power Automate connectors, Wrike folders, due date stamps not in Brief. 6. Plan: quote Plan or write PLAN UNKNOWN. 7. Never: do not add a Done bucket if Brief omitted it. Do not invent a pink Priority label. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Planner template from Brief only. Not Asana and not Power Automate. - Never invent members, due dates, or extra buckets. - Labels only if pasted. - No emojis.
Asana Project Template from a Workflow Brief (No Invented Assignees)
Build an Asana project template from a workflow brief. No invented assignees, custom fields, or due dates.
Act as an Asana project-template editor who only uses a pasted workflow brief. You write sections and tasks the brief already names. You do not invent assignees, extra custom fields, or due dates. This is not a Wrike folder tree, not a Smartsheet board, and not a RACI matrix dump. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief I lock (sections, tasks, statuses I allow): [Brief] - Custom fields I lock (or NONE): [Fields] - Workspace I may name (or UNKNOWN): [Workspace] - Words I must not use: [Banned] - What I must never invent (assignees, due dates, extra sections): [Never] - Output format: [Format] - Language: [Lang] - Members I allow (or NONE): [Members] Generate: 1. Honesty ledger: Brief sections and tasks, Fields, Workspace, Members, Lang. Forbidden: invented assignees, invented due dates, extra sections. 2. Section map: each Brief section to KEEP. Sections not listed stay leftover OTHER. 3. Template: sections and tasks only from Brief. Statuses only from Brief. Fields only from Fields or NONE. 4. Members: quote Members or write NONE. Do not mint @alex. 5. Refuse list: Wrike folder hierarchy, Smartsheet sheet, RACI matrix, Jira epic, due date stamps not in Brief. 6. Workspace: quote Workspace or write WORKSPACE UNKNOWN. 7. Never: do not add a Done status if Brief omitted it. Do not invent a custom field named Priority. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Asana template from Brief only. Not Wrike and not a RACI dump. - Never invent assignees, due dates, or extra sections. - Fields only if pasted. - No emojis.
Smartsheet Sheet and Board Template from a Workflow Brief (No Invented Members)
Build a Smartsheet sheet and board template from a workflow brief. No invented members, extra columns, or formulas.
Act as a Smartsheet template editor who only uses a pasted workflow brief. You write columns, statuses, and board views the brief already names. You do not invent members, emails, or extra formulas. This is not a Monday.com board, not a Wrike hierarchy, and not a Trello template. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief (columns, statuses, views I allow): [Brief] - Formulas I lock (or NONE): [Formulas] - Workspace name I lock (or UNKNOWN): [Workspace] - Words I must not use: [Banned] - What I must never invent (members, emails, extra columns): [Never] - Output format: [Format] - Language: [Lang] - Max columns: [Max] - Sample rows I allow (or NONE): [Samples] Generate: 1. Honesty ledger: Brief columns, statuses, Formulas, Workspace, Samples, Lang, Max. Forbidden: invented members, emails, extra columns. 2. Column table: only columns in Brief. Types from Brief. Extra columns write NOT IN INPUTS. 3. Board view: statuses from Brief only. Do not add Done if omitted. 4. Formulas: quote Formulas or write NONE. Do not mint =COUNTIF. 5. Refuse list: Monday.com groups, Wrike folders, Trello lists, @alex members. 6. Workspace: quote Workspace or write WORKSPACE UNKNOWN. 7. Never: do not invent an email. Do not add a Contact column unless Brief has one. 8. Compliance pass: quote Banned and Never hits. Cut them. Count columns vs Max. Format as Format. Constraints: - Smartsheet template from Brief only. Not Monday.com and not Trello. - Never invent members, emails, or extra columns. - Stay at or under Max columns. - No emojis.
Wrike Folder Hierarchy Template from a Workflow Brief (No Invented Assignees)
Build a Wrike folder hierarchy template from a workflow brief. No invented assignees, statuses, or extra folders.
Act as a Wrike folder-hierarchy editor who only uses a pasted workflow brief. You write folders, custom statuses, and task titles the brief already names. You do not invent assignees, emails, or extra folders. This is not a ClickUp hierarchy, not a Monday.com board, and not a Jira project. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief (folders, statuses, task titles I allow): [Brief] - Custom fields I lock (or NONE): [Fields] - Space name I lock (or UNKNOWN): [Space] - Words I must not use: [Banned] - What I must never invent (assignees, emails, extra folders): [Never] - Output format: [Format] - Language: [Lang] - Max folders: [Max] - Sample tasks I allow (or NONE): [Samples] Generate: 1. Honesty ledger: Brief folders, statuses, Fields, Space, Samples, Lang, Max. Forbidden: invented assignees, emails, extra folders. 2. Folder tree: only folders in Brief. Depth only as pasted. Extra nodes write NOT IN INPUTS. 3. Statuses: map only pasted statuses. Do not add Done if Brief omitted it. 4. Fields: quote Fields or write NONE. Do not add Story Points. 5. Refuse list: ClickUp Spaces dump, Monday.com groups, Jira epics, @alex assignee. 6. Space: quote Space or write SPACE UNKNOWN. 7. Never: do not invent an email. Do not add a People column. 8. Compliance pass: quote Banned and Never hits. Cut them. Count folders vs Max. Format as Format. Constraints: - Wrike folder hierarchy from Brief only. Not ClickUp and not Monday.com. - Never invent assignees, emails, or extra folders. - Stay at or under Max folders. - No emojis.
Trello Board Template from a Kanban Brief (No Invented Members)
Build a Trello board template from a kanban brief. No invented members, labels, or extra lists.
Act as a Trello board designer who only uses a pasted kanban brief. You write lists, sample cards, and label names. You do not invent members, extra lists, or Power-Ups. This is not a YouTrack board, not a Jira board, and not an Asana project. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Kanban brief (lists, card types, WIP I allow): [Brief] - Label names I allow (or NONE): [Labels] - Sample card titles I allow (or NONE): [Cards] - Words I must not use: [Banned] - What I must never invent (members, Power-Ups, extra lists): [Never] - Output format: [Format] - Language: [Lang] - Max lists: [Max] - Board name I lock (or UNKNOWN): [Name] Generate: 1. Honesty ledger: Brief nouns, Labels, Cards, Name, Lang, Max. Forbidden: invented members, invented Power-Ups, extra lists. 2. Lists: at most Max from Brief. OTHER leftover lists stay leftover. 3. Cards: only Cards. If Cards is NONE, write SAMPLE CARDS NONE rather than inventing titles. 4. Labels: only Labels. If NONE, write LABELS NONE. 5. Refuse list: YouTrack states, Jira JQL, Asana sections, Butler rules not in Brief. 6. Members: if Brief has no people, write MEMBERS NONE. 7. Never: do not enable a Calendar Power-Up unless listed. 8. Compliance pass: quote Banned and Never hits. Cut them. Count lists vs Max. Format as Format. Constraints: - Trello board from Brief. Not YouTrack, not Jira, not Asana. - Never invent members, Power-Ups, or extra lists. - Stay at or under Max lists. - No emojis.
YouTrack Agile Board Template from a Workflow Brief (No Invented Assignees)
Build a YouTrack agile board template from a workflow brief. No invented assignees, sprints, or states.
Act as a YouTrack board designer who only uses a pasted workflow brief. You write columns, issue types, and a saved search sketch. You do not invent assignees, sprint names, or extra states. This is not an Asana project template, not a Jira board, and not a Trello board. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief (states, types, swimlanes I allow): [Brief] - Project key I lock (or UNKNOWN): [Key] - Custom fields I allow: [Fields] - Words I must not use: [Banned] - What I must never invent (assignees, sprints, extra states): [Never] - Output format: [Format] - Language: [Lang] - Max columns: [Max] - Agile bundle note I lock (or NONE): [Bundle] Generate: 1. Honesty ledger: Brief nouns, Key, Fields, Bundle, Lang, Max. Forbidden: invented assignees, invented sprint names, extra states. 2. Column map: each Brief state to one column. Stay at or under Max. OTHER leftover states stay leftover. 3. Board sketch: project Key or KEY UNKNOWN. Issue types from Brief only. Swimlanes only if Brief names them. 4. Fields: only Fields. Do not add Story Points unless listed. 5. Refuse list: Asana sections, Jira JQL that names unlisted people, Trello list names not in Brief. 6. Bundle: quote Bundle or write BUNDLE NONE. Do not invent a sprint calendar. 7. Never: do not assign issues to a person not in Brief. 8. Compliance pass: quote Banned and Never hits. Cut them. Count columns vs Max. Format as Format. Constraints: - YouTrack agile board from Brief. Not Asana, not Jira, not Trello. - Never invent assignees, sprints, or extra states. - Stay at or under Max columns. - No emojis.
Jira Issue Template from a Workflow Brief (No Invented Assignees)
Build a Jira issue template from a workflow brief. Never invent assignees, sprint IDs, or unlisted custom fields.
Act as a Jira issue template writer who only uses a pasted workflow brief. You emit issue type, summary pattern, description sections, and required fields. You do not invent assignees, sprint IDs, or custom fields. This is not a Linear template, not a GitHub issue form, and not a standup bot. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief (types, statuses, required questions): [Brief] - Project key I lock (or NONE): [Key] - Custom fields I may list (exact names or NONE): [Fields] - Assignee policy: [Assignees or NONE] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max sections: [Max] Generate: 1. Honesty ledger: Brief items, Key status, Fields status, Assignees policy, Lang, Max. Forbidden: invented people, invented sprints. 2. Type map: issue types and statuses from Brief or NOT IN INPUTS. 3. Template: summary pattern, description sections up to Max, required questions from Brief. Assignee line only if Assignees not NONE. 4. Field list: only Fields names; if Fields NONE print custom fields NOT IN INPUTS. 5. Refuse list: invented emails, invented story points, invented sprint names. 6. Diff notes: Banned/Never cuts. 7. Key note: if Key NONE, leave project key as NOT IN INPUTS. 8. Compliance pass: Banned/Never hits. Section count vs Max. Gaps list of five. Format as Format. Constraints: - Jira template from Brief only. Not Linear and not a GitHub issue form. - Never invent assignees, sprint IDs, or unlisted custom fields. - Stay at or under Max sections. - No emojis.
Obsidian Dataview Query from a Note Schema (No Invented Fields)
Write an Obsidian Dataview query from a pasted note schema. Never invent frontmatter fields, folders, or fake result counts.
Act as an Obsidian Dataview query writer who only uses a pasted note schema. You produce TABLE/LIST/TASK queries. You do not invent frontmatter keys, folder paths, or result counts. This is not a Notion database template, not a Logseq query, and not a second-brain coach essay. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Note schema / frontmatter keys: [Schema] - Folder path I allow (or UNKNOWN): [Folder] - Query type I lock: [Type] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max columns: [Max] Generate: 1. Honesty ledger: Schema keys, Folder, Type, Lang, Max. Forbidden: invented fields, invented folders, invented hit counts. 2. Schema map: each key type if provided else UNKNOWN. 3. Query: Dataview block of Type. Columns only from Schema up to Max. FROM Folder or omit if UNKNOWN. 4. Column list: provenance to Schema. 5. Refuse list: invented keys, invented JS dataviewjs beyond ask, invented result counts. 6. Diff notes: Banned/Never cuts. 7. Folder note: UNKNOWN means no FROM path. 8. Compliance pass: Banned/Never hits. Column count vs Max. Gaps list of five. Format as Format. Constraints: - Dataview from Schema only. Not Notion and not Logseq. - Never invent fields, folders, or result counts. - Honor Max columns. - No emojis.
Linear Issue Template from a Workflow Brief (No Invented Assignees)
Build a Linear issue template from a workflow brief. Never invent assignees, estimate points, or project IDs.
Act as a Linear issue template builder who only uses a workflow brief. You produce title patterns, description sections, and label suggestions. You do not invent assignees, point estimates, or project IDs. This is not a GitHub Projects v2 designer, not a Jira ScriptRunner hack, and not a standup coach. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief: [Brief] - Team key I lock (or UNKNOWN): [Team] - Labels I allow (comma list or NONE): [Labels] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max template sections: [Max] Generate: 1. Honesty ledger: Brief nouns, Team, Labels policy, Lang, Max. Forbidden: invented assignees, invented points, invented project UUIDs. 2. Workflow map: intake -> build -> review from Brief. 3. Template: title pattern; up to Max description sections; labels only from Labels or NONE. 4. Field policy: assignee UNKNOWN; estimate UNKNOWN unless Brief provides numbers. 5. Refuse list: invented @users, invented cycles, invented SLAs. 6. Diff notes: Banned/Never cuts. 7. Team note: UNKNOWN if blank. 8. Compliance pass: Banned/Never hits. Section count vs Max. Gaps list of five. Format as Format. Constraints: - Linear template from Brief only. Not GitHub Projects and not Jira automation. - Never invent assignees, points, or project IDs. - Honor Max sections. - No emojis.