Asana Custom Field Map from Workflow Inventory (No Invented Assignees)

Prompt

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.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Generated Output

This image was generated using the prompt above.

Asana Custom Field Map from Workflow Inventory (No Invented Assignees) - Result

Examples

Example Input

Inventory: status Open as pasted; status In Review as pasted; field Priority as pasted. Assignees NONE. Due dates NOT IN INPUTS.
Version: Asana workspace notes 2024 as pasted (do not invent AI Studio invent)
Project: Harbor Dock Launch as pasted
Statuses: Open as pasted; In Review as pasted. Done UNKNOWN.
Fields: Priority as pasted; Dock Zone as pasted. Estimate UNKNOWN.
Banned: assignee invent, due date invent, estimate invent, API invent
Never: invent assignees, invent due dates, invent estimates, invent API keys
Format: ledger + map + project + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: status Open; status In Review; field Priority. Assignees NONE. Due dates NOT IN INPUTS. Version Asana workspace notes 2024. Project Harbor Dock Launch. Statuses Open; In Review; Done UNKNOWN. Fields Priority; Dock Zone; Estimate UNKNOWN. Lang English. Forbidden: invented assignees, due dates, estimates, API keys, assignee invent, due date invent, estimate invent, API invent.

2. Field map (Asana).
1. Status Open as pasted | field Priority as pasted | assignees NOT IN INPUTS (NONE)
2. Status In Review as pasted | field Dock Zone as pasted | due dates NOT IN INPUTS
Estimates: NOT IN INPUTS. API keys: NOT IN INPUTS.

3. Project lock. Harbor Dock Launch as pasted. Unnamed projects stay NOT IN INPUTS. Do not invent portfolio names.

4. Version lock. Asana workspace notes 2024 as pasted. AI Studio invent not used.

5. Refuse. Assignee invent: refused. Due date invent: refused. Estimate invent: refused. API invent: refused.

6. Compliance. Banned hits none. Format ledger+map+project+version+refuse+compliance. Gaps: Done status, estimate field, rule triggers, form fields, section names.

Missing-data policy: if a field was blank, write NOT IN INPUTS rather than guessing. Lock any tool version named in Inputs; if unnamed, write unknown. No invented testimonials, star ratings, or press logos. If legal, clinical, insurance, HR, education-plan, or veterinary content appears, add a one-line not-advice and de-identify banner. Quote banned-word hits and cut them. End with a gaps list of five bullets the user still owes you. Character and byte caps in the job are hard; print counts when relevant. Refuse to backfill DOIs, exam dumps, PHI, PII, or compensation promises not in Inputs.