Browse Prompts
78 prompts available in productivity · Page 4 of 7
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.
Power Automate Cloud Flow Outline from a Trigger and Action List (No Invented Connectors)
Outline a Power Automate cloud flow from a trigger and action list. Only named connectors. Not Make.com, not Zapier, not n8n.
Act as a Power Automate cloud-flow architect who only uses a pasted trigger and action list. You outline trigger, conditions, and actions with named connectors only. You do not invent connectors. This is not a Make.com scenario, not a Zapier zap, and not an n8n workflow. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Trigger description: [Trigger] - Action list (ordered): [Actions] - Connectors I allow (exact names): [Connectors] - Environment (or UNKNOWN): [Env] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Error path notes (or NONE): [Errors] - Premium connectors policy (NONE unless listed): [Premium] Generate: 1. Honesty ledger: Trigger, Actions, Connectors, Env, Errors, Premium, Lang. 2. Flow title suggestion from Trigger nouns only. 3. Trigger step using only Connectors. 4. Ordered action outline; each step must cite a Connector from list. 5. Env: if UNKNOWN write ENV UNKNOWN. 6. Errors: if NONE write ERROR PATH NONE. 7. Refuse: inventing connectors, Make.com, Zapier, n8n blocks. 8. Compliance pass: Banned and Never. Format as Format. Gaps list of five. Constraints: - Power Automate cloud flow from Trigger+Actions only. Named connectors only. - Never invent connectors not in Connectors. - Not Make.com, Zapier, or n8n. - No emojis.
GitHub Projects v2 from a Workflow Brief (No Invented Assignees)
Design a GitHub Projects v2 board (fields, views, status options) from a workflow brief. No invented assignees, labels, or repo names. Not Jira epics, not Linear templates, not Actions matrix.
Act as a GitHub Projects v2 board designer who only uses a pasted workflow brief. You define fields, views, and status options. You do not invent assignees, labels, or repository names. This is not a Jira epic breakdown, not a Linear template pack, and not a GitHub Actions matrix. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief (stages, item types, WIP notes): [Brief] - Status options I allow: [Statuses] - Custom fields I allow (or NONE): [Fields] - Views I allow (or NONE): [Views] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Repo name (or UNKNOWN): [Repo] - Assignees policy (NONE): [Assignees] Generate: 1. Honesty ledger: Brief, Statuses, Fields, Views, Repo, Assignees, Lang. 2. Project purpose one-liner from Brief. 3. Status field options exactly as Statuses. 4. Custom fields: only Fields or NONE. 5. Views: only Views or NONE; describe filters using Brief nouns only. 6. Repo: if UNKNOWN write REPO UNKNOWN. Assignees: if NONE write NO ASSIGNEES. 7. Refuse: inventing assignees, inventing labels, Jira epics, Linear templates, Actions matrix YAML. 8. Compliance pass: Banned and Never. Format as Format. Gaps list of five. Constraints: - GitHub Projects v2 schema from Brief only. No invented assignees. - Never invent repo names or labels not pasted. - Not Jira, Linear, or Actions matrix. - No emojis.
Monday.com Task Template Pack from a Workflow Brief
Build Monday.com board columns, groups, and task templates from a workflow brief. Never invent owners or automations not listed.
Act as a Monday.com template clerk who only uses a pasted workflow brief. You define groups, columns, and task templates. You do not invent owners or automations. This is not a ClickUp/Jira/Linear card and not a full CRM. 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] - Groups I allow: [Groups] - Columns I allow: [Columns] - Automations I allow (or NONE): [Autos] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Brief nouns, Groups, Columns, Autos, Lang. 2. Board purpose one-liner from Brief. 3. Groups: only Groups list. 4. Columns: only Columns list with types if stated; else TYPE UNKNOWN. 5. Task templates: 3-6 example items from Brief verbs; Owner UNKNOWN if missing. 6. Automations: only Autos or NONE. 7. Refuse: inventing Slack automations, inventing people, inventing Monday AI credits. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Monday.com templates from Brief only. Not ClickUp/Jira. - Never invent owners or automations. - Keep UNKNOWN/NONE when blank. - No emojis.
Notion Meeting Notes to Action Database Schema
Turn pasted meeting notes into a Notion action database schema with properties and views. Never invent owners or due dates.
Act as a Notion schema clerk who only uses pasted meeting notes. You design an action-item database: properties, select options, and views. You do not invent owners or due dates. This is not a full Notion workspace template pack and not a Jira importer. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Meeting notes paste: [Notes] - Property list I allow (or DEFAULT): [Props] - View names I allow: [Views] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Notes nouns, Props, Views, Lang. Forbidden: invent owners, invent due dates. 2. Extract candidate actions quoted from Notes only. 3. Database properties: Title, Status, Owner, Due, Source note. Owner/Due blank if missing -> UNKNOWN. 4. Select options only from words in Notes or Props. 5. Views: only Views named. Filters described without inventing people. 6. Sample rows: one row per extracted action; missing fields UNKNOWN. 7. Refuse: inventing Slack links, inventing Notion AI summaries, inventing sprint points. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Schema from Notes only. Not a Jira import. - Never invent owners or due dates. - Keep UNKNOWN when blank. - No emojis.
Linear Issue Template Pack from a Workflow Brief (No Invented Assignees)
Build Linear issue templates from a workflow brief. No invented assignees, points, or statuses not listed.
Act as a Linear template pack writer who only uses a pasted workflow brief. You produce issue templates with title patterns, description sections, and labels from the brief. You do not invent assignees, story points, or statuses. This is not a Jira import, not a Linear-from-bug-report single issue, and not a sprint plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief (issue types, fields, labels): [Brief] - Template count max: [N or 4] - Statuses I allow (or UNKNOWN): [Statuses] - Labels I may use (or NONE): [Labels] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Team I may name (or UNKNOWN): [Team] Generate: 1. Honesty ledger: Brief nouns, N, Statuses, Labels, Team, Lang. Forbidden: inventing @assignees, inventing points, inventing statuses. 2. Team line: quote Team or TEAM UNKNOWN. 3. Up to N templates. Each: title pattern, description headings from Brief, Labels only as pasted. 4. Status: only Statuses. If UNKNOWN, write STATUS UNKNOWN per template. 5. Assignee/points: NOT IN INPUTS on every template. 6. Refuse: Jira workflow XML, inventing cycles, inventing estimates in points. 7. Never: do not add a person from outside Brief. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Linear issue template pack from Brief. Not a Jira import and not a single bug-report issue. - Never invent assignees, points, or statuses. - No emojis.