Linear Issue Template Field Map from Workflow Inventory (No Invented Assignees/Estimates)

Prompt

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.

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.

Linear Issue Template Field Map from Workflow Inventory (No Invented Assignees/Estimates) - Result

Examples

Example Input

Inventory: states Triage as pasted; In Progress as pasted; labels Harbor Dock as pasted; Warehouse PPE as pasted. Assignees NONE. Estimate points NOT IN INPUTS.
Version: Linear issue template notes 2024 as pasted (do not invent Cycles v3 invent)
Team: Harbor Platform as pasted
Template: Dock Incident Intake as pasted
Priorities: Urgent as pasted; High as pasted. Low UNKNOWN.
Banned: guaranteed sprint fit, assignee invent, estimate invent, project UUID invent
Never: invent assignees, invent estimate points, invent project IDs, invent cycle names
Format: ledger + field map + priorities + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: states Triage; In Progress; labels Harbor Dock; Warehouse PPE. Assignees NONE. Estimate points NOT IN INPUTS. Version Linear issue template notes 2024. Team Harbor Platform. Template Dock Incident Intake. Priorities Urgent; High; Low UNKNOWN. Lang English. Forbidden: invented assignees, estimate points, project IDs, cycle names, guaranteed sprint fit, assignee invent, estimate invent, project UUID invent.

2. Field map table (Linear issue template).
1. State Triage as pasted | template field status cue | source Inventory
2. State In Progress as pasted | template field status cue | source Inventory
3. Label Harbor Dock as pasted | template label cue | source Inventory
4. Label Warehouse PPE as pasted | template label cue | source Inventory
Assignees: NONE so write NOT IN INPUTS. Estimate points: NOT IN INPUTS.

3. Priorities lock. Urgent as pasted. High as pasted. Low UNKNOWN so write NOT IN INPUTS. Do not invent Medium priority.

4. Version lock. Linear issue template notes 2024 as pasted. Cycles v3 invent not used.

5. Refuse. Assignee invent: refused. Estimate invent: refused. Project UUID invent: refused. Guaranteed sprint fit: refused. Cycle name invent: refused.

6. Compliance. Banned hits none. Format ledger+field map+priorities+version+refuse+compliance. Gaps: Low priority decide, estimate policy, project link, cycle naming, description body stub.

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.