#no invented assignees
13 prompts found
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.