⚡ Productivity
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.
0Reviews
Prompt
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.
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.
Examples
Example Input
Inventory: label bug as pasted group Defects as pasted; label harbor-dock as pasted group Product as pasted. Priority label NONE. Cycle label NOT IN INPUTS. Version: Linear API GraphQL 2024 as pasted (do not invent 2026) TeamKey: HBR as pasted Required: bug as pasted. harbor-dock optional. Banned: guaranteed sprint, @harbor invent, project UUID invent, points invent Never: invent assignee emails, invent project ids, invent cycle dates, invent points Format: ledger + table + required + version + refuse + compliance Lang: English
Example Output
1. Ledger. Inventory: bug group Defects; harbor-dock group Product. Priority NONE. Cycle NOT IN INPUTS. Version Linear API GraphQL 2024. TeamKey HBR. Required bug; harbor-dock optional. Lang English. Banner: not a sprint commitment; not an OKR forecast. Forbidden: invented assignee emails, project ids, cycle dates, points, guaranteed sprint, @harbor invent, project UUID invent, points invent. 2. Label map. 1. bug | group Defects as pasted | required yes as Required. 2. harbor-dock | group Product as pasted | required no. Priority NONE so no priority row. Cycle NOT IN INPUTS so no cycle row. Project IDs not invented. 3. Required set. bug only. harbor-dock optional. No invented third required label. 4. Version lock. Linear API GraphQL 2024 as pasted. 2026 objects not used. Team UUID NOT IN INPUTS. 5. Refuse. @harbor invent: refused. Project UUID invent: refused. Cycle end date invent: refused. Story points invent: refused. Guaranteed sprint: refused. 6. Compliance. Banned hits none. Format ledger+table+required+version+refuse+compliance. Gaps: cycle label decision, priority label, team UUID, assignee policy, estimate field. 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.