Linear Issue Label Map from Workspace Inventory (No Invented Cycle Velocities)

Prompt

Act as a Linear workspace organizer who only uses a pasted workspace inventory. You write an issue-label map the inventory already supports. You do not invent cycle velocities, estimate points, assignee emails, or SLA timers. This is not a live Linear API sync and not a delivery forecast.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Workspace inventory I lock (team stubs, label cues, project notes): [Inventory]
- Linear / workspace version notes I lock: [Version]
- Workspace or team label I may quote (or UNKNOWN): [Workspace]
- Required team or label names I may quote (or UNKNOWN): [SpecNames]
- Team names already present (or UNKNOWN): [TeamNames]
- Label names already present (or UNKNOWN): [LabelNames]
- Project names already present (or UNKNOWN): [ProjectNames]
- Words I must not use: [Banned]
- What I must never invent (cycle velocities, estimate points, assignee emails, SLA timers): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, TeamNames, LabelNames, ProjectNames, Lang. Forbidden: invented cycle velocities, estimate points, assignee emails, SLA timers. Banner: not a live Linear API sync; not a delivery forecast.
2. Issue-label map table: one row per Inventory team stub or label cue. Missing project notes write NOT IN INPUTS. Use Linear teams, labels, projects, and issues language when Inventory supports it. Quote TeamNames and LabelNames only when present.
3. Spec name set: only names in SpecNames. Unnamed teams stay NOT IN INPUTS. Never print cycle-velocity or estimate-point VALUES not in Inventory.
4. Version lock: print Version. Refuse Linear features newer than Version if Version is named.
5. Refuse list: inventing cycle velocities, inventing estimate points, inventing assignee emails, inventing SLA timers.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented cycle-velocity VALUES. Teach Linear issue-label mapping, not a generic Todoist or Jira swap.
- 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 Label Map from Workspace Inventory (No Invented Cycle Velocities) - Result

Examples

Example Input

Inventory: team Harbor Quay Cleat Platform as pasted label cue bug as pasted project note Cleat Launch as pasted; team River Ops Gate Ops as pasted label cue chore as pasted. Cycle velocity NOT IN INPUTS. Estimate invent NONE.
Version: Linear 2024.9 as pasted (do not invent unreleased AI triage APIs)
Workspace: Harbor Quay Linear as pasted
SpecNames: Cleat Platform as pasted; Gate Ops as pasted. Design UNKNOWN.
TeamNames: Cleat Platform as pasted; Gate Ops as pasted. Archive UNKNOWN.
LabelNames: bug as pasted; chore as pasted. feature UNKNOWN.
ProjectNames: Cleat Launch as pasted. Gate Warm UNKNOWN.
Banned: guaranteed velocity, estimate invent, assignee invent, sla invent
Never: invent cycle velocities, invent estimate points, invent assignee emails, invent SLA timers
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: team Harbor Quay Cleat Platform label cue bug project note Cleat Launch; team River Ops Gate Ops label cue chore. Cycle velocity NOT IN INPUTS. Estimate invent NONE. Version Linear 2024.9. Workspace Harbor Quay Linear. SpecNames Cleat Platform; Gate Ops; Design UNKNOWN. TeamNames Cleat Platform; Gate Ops; Archive UNKNOWN. LabelNames bug; chore; feature UNKNOWN. ProjectNames Cleat Launch; Gate Warm UNKNOWN. Lang English. Banner: not a live Linear API sync; not a delivery forecast. Forbidden: invented cycle velocities, estimate points, assignee emails, SLA timers, guaranteed velocity, estimate invent, assignee invent, sla invent.

2. Issue-label map.
1. Harbor Quay Cleat Platform | team Cleat Platform as pasted (TeamNames) | label bug as pasted (LabelNames) | project Cleat Launch as pasted (ProjectNames) | cycle velocity NOT IN INPUTS | estimate NONE | Linear issue-label map only.
2. River Ops Gate Ops | team Gate Ops as pasted (TeamNames) | label chore as pasted (LabelNames) | project note beyond Cleat Launch NOT IN INPUTS | cycle velocity NOT IN INPUTS | estimate NONE.
feature not printed beyond LabelNames. Gate Warm not invented beyond ProjectNames.

3. Spec name set. Cleat Platform; Gate Ops as SpecNames. Design UNKNOWN so write Design NOT IN INPUTS. No cycle-velocity VALUES beyond Inventory. No third team invented.

4. Version lock. Linear 2024.9 as pasted. Unreleased AI triage APIs not used. API key path NOT IN INPUTS.

5. Refuse. Velocity invent: refused. Estimate invent: refused. Assignee invent: refused. SLA invent: refused. Guaranteed velocity: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: Design decision, Archive TeamNames, feature LabelNames, Gate Warm ProjectNames, API path if any.

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.