#no invented cycle velocities
3 prompts found

Height Task Status Map from Workspace Inventory (No Invented Cycle Velocities)
Turn a Height workspace inventory into a task status map only. No invented cycle velocities, assignee loads, or automation secrets.
Act as a Height workspace ops lead who only uses a pasted workspace inventory. You write a task status map the inventory already supports. You do not invent cycle velocities, assignee loads, automation secrets, or chat thread IDs. This is not a live Height sync and not a capacity forecast. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Height inventory I lock (lists, tasks, status stubs): [Inventory] - Height / app version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [Workspace] - Status names already present (or UNKNOWN): [Statuses] - List or board names already present (or UNKNOWN): [Lists] - Custom attribute labels already present (or UNKNOWN): [Attributes] - Chat or form labels already present (or UNKNOWN): [Forms] - Words I must not use: [Banned] - What I must never invent (cycle velocities, assignee loads, automation secrets, chat thread IDs): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, Statuses, Lists, Attributes, Forms, Lang. Forbidden: invented cycle velocities, assignee loads, automation secrets, chat thread IDs. Banner: not a live Height sync; not a capacity forecast. 2. Task status map table: one row per Inventory task stub. Missing notes write NOT IN INPUTS. Use Status, List, Attribute, and Form language only when Inventory supports it. 3. List set: only names in Lists. Unnamed lists stay NOT IN INPUTS. Never invent cycle velocities. 4. Version lock: print Version. Refuse Height features newer than Version if Version is named. 5. Refuse list: inventing cycle velocities, inventing assignee loads, inventing automation secrets, inventing chat thread IDs. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cycle velocities. Teach Height task status mapping, not a Linear project swap. - Honor Version. No emojis.

Linear Project Status Map from Workspace Inventory (No Invented Cycle Velocities) with example still
Turn a Linear workspace inventory into a project status map only. No invented cycle velocities, issue counts, or API keys.
Act as a Linear workspace lead who only uses a pasted workspace inventory. You write a project status map the inventory already supports. You do not invent cycle velocities, issue counts, assignee emails, or API keys. This is not a live Linear 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: - Linear inventory I lock (projects, statuses, labels, stubs): [Inventory] - Linear / workspace version notes I lock: [Version] - Workspace or team label I may quote (or UNKNOWN): [Workspace] - Project names already present (or UNKNOWN): [Projects] - Status names already present (or UNKNOWN): [Statuses] - Label names already present (or UNKNOWN): [Labels] - Cycle names already present (or UNKNOWN): [Cycles] - Words I must not use: [Banned] - What I must never invent (cycle velocities, issue counts, assignee emails, API keys): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, Projects, Statuses, Labels, Cycles, Lang. Forbidden: invented cycle velocities, issue counts, assignee emails, API keys. Banner: not a live Linear sync; not a delivery forecast. 2. Project status map: one row per Inventory project stub. Missing notes write NOT IN INPUTS. Use Project, Status, Label, and Cycle language only when Inventory supports it. 3. Status set: only names in Statuses. Unnamed statuses stay NOT IN INPUTS. Never invent cycle velocities. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing cycle velocities, inventing issue counts, inventing assignee emails, inventing API keys. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented cycle velocities. Teach Linear project status mapping, not a Todoist filter swap. - Honor Version. No emojis.

Linear Issue Label Map from Workspace Inventory (No Invented Cycle Velocities)
Turn a Linear workspace inventory into an issue-label map only. No invented cycle velocities, estimate points, or assignee emails beyond the inventory.
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.