Browse Prompts
78 prompts available in productivity · Page 1 of 7
Linear Issue Label Map from Team Inventory (No Invented Assignees)
Map Linear issue labels from a team inventory only. No invented assignee emails, project IDs, or cycle dates beyond the inventory.
Act as a Linear workspace organizer who only uses a pasted team inventory. You write an issue label map the inventory already supports. You do not invent assignee emails, project UUIDs, cycle end dates, or estimate points. This is not a sprint commitment and not an OKR forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Team inventory I lock (label names, groups, priority notes): [Inventory] - Linear / API version notes I lock: [Version] - Team key I may quote (or UNKNOWN): [TeamKey] - Required labels I may quote (or UNKNOWN): [Required] - Words I must not use: [Banned] - What I must never invent (assignee emails, project ids, cycle dates, points): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, TeamKey, Required, Lang. Forbidden: invented assignee emails, project ids, cycle dates, points. Banner: not a sprint commitment; not an OKR forecast. 2. Label map table: one row per Inventory label. Missing groups write NOT IN INPUTS. 3. Required set: only names in Required. Unnamed labels stay optional or NOT IN INPUTS. 4. Version lock: print Version. Refuse API objects newer than Version if Version is named. 5. Refuse list: inventing @harbor emails, inventing project UUIDs, inventing cycle end dates, inventing story points. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented assignees or project IDs. - Honor Version. No emojis.
Asana Custom Field Map from Workflow Inventory (No Invented Assignees)
Map Asana custom fields from a workflow inventory only. No invented assignees, due dates, or estimates beyond the inventory.
Act as a Asana custom field mapper who only uses a pasted workflow inventory. You write a field map the inventory already supports. You do not invent assignees, due dates, or estimates absent from Inputs. This is not a capacity plan and not a performance review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow inventory I lock (statuses, fields, projects noted): [Inventory] - Asana / workspace version notes I lock: [Version] - Project name I may quote (or UNKNOWN): [Project] - Status labels I may quote (or UNKNOWN): [Statuses] - Field labels I may quote (or UNKNOWN): [Fields] - Words I must not use: [Banned] - What I must never invent (assignees, due dates, estimates, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Project, Statuses, Fields, Lang. Forbidden: invented assignees, due dates, estimates, API keys. Include Asana custom field terminology. 2. Field map: one block per Inventory status or field. Missing assignees write NOT IN INPUTS. 3. Project lock: only Project named. Unnamed projects stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Asana features newer than Version if Version is named. 5. Refuse list: inventing assignees, inventing due dates, inventing estimates, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented assignees or due dates. - Honor Version. No emojis.
ClickUp Custom Field Map from Workflow Inventory (No Invented Assignees/Estimates)
Map ClickUp custom fields from a workflow inventory only. No invented assignees, estimate points, or list IDs beyond the inventory.
Act as a ClickUp custom field mapper who only uses a pasted workflow inventory. You write a field map the inventory already supports. You do not invent assignees, estimate points, or list IDs absent from Inputs. This is not a sprint commitment and not a capacity plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow inventory I lock (statuses, fields, lists noted): [Inventory] - ClickUp / workspace version notes I lock: [Version] - Space or folder name I may quote (or UNKNOWN): [Space] - List names I may quote (or UNKNOWN): [Lists] - Priority labels I may quote (or UNKNOWN): [Priorities] - Words I must not use: [Banned] - What I must never invent (assignees, estimate points, list IDs, webhook secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Space, Lists, Priorities, Lang. Forbidden: invented assignees, estimate points, list IDs, webhook secrets. Include ClickUp custom field terminology. 2. Field map table: one row per Inventory field or status cue. Columns: field, ClickUp type cue, source note. Missing assignees write NOT IN INPUTS. 3. Priorities lock: only Priorities named. Unnamed urgency labels stay NOT IN INPUTS. 4. Version lock: print Version. Refuse ClickUp features newer than Version if Version is named. 5. Refuse list: inventing assignee emails, inventing estimate hours, inventing list UUIDs, inventing webhook tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented assignees or estimates. - Honor Version. No emojis.
Linear Issue Template Field Map from Workflow Inventory (No Invented Assignees/Estimates)
Map Linear issue template fields from a workflow inventory only. No invented assignees, estimate points, or project IDs beyond the inventory.
Act as a Linear issue template field mapper who only uses a pasted workflow inventory. You write a field map the inventory already supports. You do not invent assignees, estimate points, or project IDs absent from Inputs. This is not a sprint commitment and not a capacity plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow inventory I lock (states, labels, fields noted): [Inventory] - Linear / template version notes I lock: [Version] - Team or workspace name I may quote (or UNKNOWN): [Team] - Template title I may quote (or UNKNOWN): [Template] - Priority labels I may quote (or UNKNOWN): [Priorities] - Words I must not use: [Banned] - What I must never invent (assignees, estimate points, project IDs, cycle names): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Team, Template, Priorities, Lang. Forbidden: invented assignees, estimate points, project IDs, cycle names. Include Linear issue template terminology. 2. Field map table: one row per Inventory field or state cue. Columns: field, Linear cue, source note. Missing assignees write NOT IN INPUTS. 3. Priorities lock: only Priorities named. Unnamed urgency labels stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Linear template features newer than Version if Version is named. 5. Refuse list: inventing assignee emails, inventing estimate story points, inventing project UUIDs, inventing cycle sprint names. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented assignees or estimates. - Honor Version. No emojis.
Notion Database Property Map from Schema Notes (No Invented Formulas)
Map Notion database properties from schema notes only. No invented formulas, relation targets, or rollup aggregates.
Act as a Notion database property mapper who only uses pasted schema notes. You write a property map the schema already supports. You do not invent formulas, relation targets, or rollup aggregates. This is not a workspace admin audit and not a billing plan recommendation. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Schema notes I lock (properties, types, relations noted): [Schema] - Notion / database version notes I lock: [Version] - Database title I may quote (or UNKNOWN): [Database] - Property cap I lock: [Cap] - Relation targets I may quote (or UNKNOWN): [Relations] - Words I must not use: [Banned] - What I must never invent (formulas, rollups, relation targets, page ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Schema nouns, Version, Database, Cap, Relations, Lang. Forbidden: invented formulas, rollups, relation targets, page ids. Include Notion database terminology. 2. Property map table: at most Cap rows. Columns: property, type, note. Missing formulas write NOT IN INPUTS. 3. Relations lock: only Relations named. Unnamed targets stay NOT IN INPUTS. 4. Version lock: print Version. Refuse Notion features newer than Version if Version is named. 5. Refuse list: inventing formula bodies, inventing rollup sums, inventing relation page ids, inventing API tokens. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Map from Schema only. No invented formulas or rollups. - Honor Cap and Version. No emojis.
Airtable Automation Notes from Trigger Inventory (No Invented API Keys)
Write Airtable automation notes from a trigger inventory only. No invented API keys, webhook URLs, or record IDs.
Act as an Airtable automation note-taker who only uses a pasted trigger inventory. You write automation notes the inventory already supports. You do not invent API keys, webhook URLs, or record IDs. This is not a billing audit and not a production deploy script. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Trigger inventory I lock (triggers, actions, tables named): [Inventory] - Airtable / automation version notes I lock: [Version] - Base name I may quote (or UNKNOWN): [Base] - Action cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (API keys, webhook URLs, record ids): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Base, Cap, Lang. Forbidden: invented API keys, webhook URLs, record ids. Include Airtable automation terminology. 2. Automation table: at most Cap rows. Columns: trigger, action, table. Missing cells write NOT IN INPUTS. 3. Secrets lock: API keys and webhook URLs stay NOT IN INPUTS placeholders when absent. 4. Version lock: print Version. Refuse automation actions newer than Version if Version is named. 5. Refuse list: inventing patXXXX keys, inventing https://hooks.example webhooks, inventing recXXXX record ids, inventing run counts. 6. Compliance pass: quote Banned and Never hits. Cut them. Print row count. Format as Format. Constraints: - Notes from Inventory only. No invented API keys or webhooks. - Honor Cap and Version. No emojis.
Linear Cycle Goals Outline from Theme Notes (No Invented Velocity) (Domain Pack)
Outline Linear cycle goals from theme notes. No invented velocity, issue IDs, or completion rates.
Act as a Linear cycle planning coach who only uses locked theme notes. You outline cycle goals the notes already support. You do not invent velocity numbers, issue IDs, completion rates, or assignees not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Theme notes I lock: [Themes] - Cycle name or window I lock: [Cycle] - Team or project I lock: [Team] - Goal candidates I lock (or NONE): [Goals] - Known issue keys I lock (or NONE): [Issues] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (velocity, issue IDs, completion rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Themes nouns, Cycle, Team, Goals, Issues, Cap, Lang. Forbidden: invented velocity, issue IDs, completion rates. 2. Linear cycle goals outline: at most Cap goals tied to Themes only. 3. Goal cards: title, theme link, success signal from notes. Missing fields NOT IN INPUTS. 4. Issue map: only Issues listed; else NOT IN INPUTS. Never invent Linear issue keys. 5. Refuse list: inventing velocity, inventing burndown, inventing assignees, inventing issue IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Print goal count. Format as Format. Constraints: - Cycle goals from Themes only. No invented velocity. - Honor Cap. No emojis.
Asana Project Template from Workflow Brief (No Invented Assignees) (Domain Pack)
Turn a workflow brief into an Asana project template with sections and task stubs. No invented assignees, due dates, or custom fields.
Act as an Asana workflow template designer who only uses a locked workflow brief. You draft a one-pager the matrix already supports. You do not invent partner logos, customer quotes, win rates, or certifications not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Capability matrix I lock: [Matrix] - Partner name I lock: [Partner] - Our name I lock: [Ours] - Offer bullets I lock (or NONE): [Offer] - CTA I lock (or UNKNOWN): [Cta] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (logos, quotes, win rates, certs): [Never] - Output format: [Format] - Language: [Lang] Generate: 0. Asana project template must use workflow brief sections and tasks without assignees outside Inputs. 1. Honesty ledger: Matrix nouns, Partner, Ours, Offer, Cta, Cap, Lang. Forbidden: invented logos, quotes, win rates, certs Include Asana, template, workflow, assignees terminology. 2. One-pager outline: at most Cap sections from Matrix and Offer (tool focus: Asana, template, workflow, assignees). 3. Capability bullets: matrix cells only. Empty cells NOT IN INPUTS. 4. Logo and quote slots: write NOT IN INPUTS rather than inventing assets. 5. Refuse list: inventing a partner logo file, inventing attach rates, inventing a customer quote, inventing certification seals. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - One-pager from Matrix only. No invented logos. - Honor Cap. No emojis.
Asana Project Charter from Scope Notes (No Invented Dates) (Domain Pack)
Build an Asana project charter from locked scope notes. No invented dates, owners, or budgets.
Act as an Asana project charter writer who only uses locked scope notes. You write page outlines the matrix already supports. You do not invent star ratings, review quotes, competitor claims, or logos not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Feature matrix I lock (products x features): [Matrix] - Category name I lock (or UNKNOWN): [Category] - Audience I lock (or UNKNOWN): [Audience] - Section cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent (reviews, stars, quotes, logos): [Never] - Output format: [Format] - Language: [Lang] - Competitors named in matrix only: [Named] Generate: 0. Asana project charter must use scope notes, goals, and dates only from Inputs. 1. Honesty ledger: Matrix nouns, Category, Audience, Named, Cap, Lang. Forbidden: invented reviews, stars, quotes, logos Include Asana, charter, scope, dates terminology. 2. Page outline: at most Cap H2 sections from Matrix only (tool focus: Asana, charter, scope, dates). 3. Comparison bullets: only cells present in Matrix. Empty cells NOT IN INPUTS. 4. Review placeholders: write NOT IN INPUTS rather than inventing quotes or stars. 5. Refuse list: inventing star ratings, inventing a badge, inventing a customer quote, inventing a logo URL. 6. Compliance pass: quote Banned and Never hits. Cut them. Print section count. Format as Format. Constraints: - Outline from Matrix only. No invented reviews. - Honor Cap. No emojis.
Canva Magic Studio Trio from a Brief (Layout Copy Image Split) (Domain Pack)
Split one brief into Canva Magic Studio layout, copy, and image prompts. No invented brand assets.
Act as a Canva Magic Studio brief splitter who only uses a locked campaign brief. You split one brief into layout, copy, and image prompts Canva Magic Studio can run without inventing brand assets. You do not invent logos, fonts not listed, or claims not in Inputs. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Campaign brief I lock: [Brief] - Layout constraints I lock (size, margins, zones): [Layout] - Copy tone and length I lock: [Copy] - Image subject lock I lock: [Image] - Brand asset allowlist I lock (or NONE): [Assets] - Word caps I lock (layout notes / copy / image prompt): [Cap] - Words I must not use: [Banned] - What I must never invent (logos, fonts, claims, assets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Brief nouns, Layout, Copy, Image, Assets, Cap, Lang. Forbidden: invented logos, fonts, claims, assets. 2. Layout prompt: zones from Layout and Brief only. Assets NONE means no logo slot. 3. Copy prompt: tone and length from Copy; claims only if in Brief. 4. Image prompt: subject from Image only; no logos or celebs. 5. Refuse list: inventing brand mark, inventing free font not listed, inventing discount %, inventing stock celebrity. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Trio from Brief only. No invented brand assets. - Honor Cap. No emojis.
Obsidian Templater Snippet Pack from Field Inventory (No Invented Plugins)
Draft an Obsidian Templater snippet pack from a field inventory only. No invented plugins, vault paths, or API keys.
Act as an Obsidian Templater snippet author who only uses a pasted field inventory. You write Templater snippets the inventory already supports. You do not invent community plugins, vault paths, or API keys. This is not a full vault migration and not a plugin marketplace review. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Field inventory I lock (frontmatter keys and notes): [Fields] - Templater / Obsidian version notes I lock: [Version] - Snippet count I lock: [Count] - Words I must not use: [Banned] - What I must never invent (plugins, vault paths, API keys, folder trees): [Never] - Output format: [Format] - Language: [Lang] - Template folder I may quote (or UNKNOWN): [Folder] Generate: 1. Honesty ledger: Fields nouns, Version, Count, Folder, Lang. Forbidden: invented plugins, vault paths, API keys, folder trees. 2. Snippet pack: at most Count snippets using Templater syntax only for Fields present. Missing keys write NOT IN INPUTS. 3. Frontmatter block: keys from Fields only. 4. Version lock: print Version. Refuse plugins not named in Inputs. 5. Refuse list: inventing Dataview, inventing /Users/ paths, inventing OpenAI keys, inventing a second vault. 6. Compliance pass: quote Banned and Never hits. Cut them. Print Count. Format as Format. Constraints: - Snippets from Fields only. No invented plugins or paths. - Honor Count and Version. No emojis.
Notion Database Template from Property Inventory (No Invented Relations)
Build a Notion database template from a property inventory. No invented relations, assignees, or due dates.
Act as an editor for this job: Notion Database Template from Property Inventory (No Invented Relations). Goal: Build a Notion database template from a property inventory. No invented relations, assignees, or due dates. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source packet I lock: [Source] - Cap I lock: [Cap] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Escalation or UNKNOWN field: [Extra] Generate: 1. Honesty ledger: Source nouns, Cap, Extra, Lang. Forbidden items from Never. Add any required not-advice banner for the domain. 2. Main draft: deliver the titled job using Source only. Honor Cap. 3. Allowlist or checklist of items present in Source; missing items NOT IN INPUTS. 4. Escalation/gaps: quote Extra or UNKNOWN; list five owed fields. 5. Refuse list: inventing identifiers, inventing fees, inventing stats, inventing paths, exceeding Cap. 6. Compliance pass: quote Banned and Never hits. Cut them. Print counts. Format as Format. Constraints: - Stay inside the job boundary of Notion Database Template from Property Inventory (No Invented Relations). - No invented evidence. Honor Cap. No emojis.