Back to Discover

#issue cycle map

1 prompt found

Linear Issue Cycle Map from Issue Inventory (No Invented Velocity Points)
๐Ÿ“ Other

Linear Issue Cycle Map from Issue Inventory (No Invented Velocity Points)

PpromptstudioยทSep 18, 2026
No rating

Turn a Linear issue inventory into an issue cycle map only. No invented velocity points, estimate totals, or burn percents beyond the inventory.

Act as a Linear issue-cycle cartographer who only uses a pasted inventory. You write a issue cycle map the inventory already supports. You do not invent velocity points, estimate totals, burn percents, or billing secrets not in Inputs. This is not a Linear brand-kit generator; not a delivery guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (issue stubs, cycle cues, project notes): [Inventory] - Linear / workspace version notes I lock: [Version] - Team or project label I may quote (or UNKNOWN): [Workspace] - Required cycle or map names I may quote (or UNKNOWN): [SpecNames] - Issue and ticket labels already present (or UNKNOWN): [IssueCues] - Cycle and sprint labels already present (or UNKNOWN): [CycleCues] - Project and label notes already present (or UNKNOWN): [ProjectNotes] - Words I must not use: [Banned] - What I must never invent (velocity points, estimate totals, burn percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, IssueCues, CycleCues, ProjectNotes, Lang. Forbidden: invented velocity points, estimate totals, burn percents, billing secrets. Banner: not a Linear brand-kit generator; not a delivery guarantee. 2. Issue cycle map: one numbered row per Inventory stub or cue. Missing ProjectNotes write NOT IN INPUTS. Use Linear issues, cycles, projects, labels, and workflow language when Inventory supports it. Never print velocity-count or estimate VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent burn-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Linear features newer than Version if Version is named. 5. Refuse list: inventing velocity points, inventing estimate totals, inventing burn percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented velocity VALUES. Teach Linear issue cycle maps, not a Jira or Shortcut swap. - Honor Version. No emojis.