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

Prompt

Act as a Linear delivery cartographer who only uses a pasted issue inventory. You write a project cycle map the inventory already supports. You do not invent cycle velocity, estimate points, assignee emails, or private workspace URLs not in Inputs. This is not a Linear billing estimate and not a sprint velocity certificate.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Issue cycle inventory I lock (project stubs, issue cues, state notes): [Inventory]
- Linear / workspace version notes I lock: [Version]
- Team or workspace label I may quote (or UNKNOWN): [Workspace]
- Required project or cycle names I may quote (or UNKNOWN): [SpecNames]
- Project titles already present (or UNKNOWN): [ProjectCues]
- Issue and label cues already present (or UNKNOWN): [IssueCues]
- Workflow state notes already present (or UNKNOWN): [StateNotes]
- Words I must not use: [Banned]
- What I must never invent (cycle velocity, estimate points, assignee emails, private URLs): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ProjectCues, IssueCues, StateNotes, Lang. Forbidden: invented cycle velocity, estimate points, assignee emails, private URLs. Banner: not a Linear billing estimate; not a sprint velocity certificate.
2. Cycle map table: one row per Inventory project stub or issue cue. Missing StateNotes write NOT IN INPUTS. Use Linear Projects, Cycles, Issues, Labels, and workflow states language when Inventory supports it. Never print velocity or estimate-point VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed projects stay NOT IN INPUTS. Never invent assignee-email VALUES not in Inventory.
4. Version lock: print Version. Refuse Linear features newer than Version if Version is named.
5. Refuse list: inventing cycle velocity, inventing estimate points, inventing assignee emails, inventing private URLs.
6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Map from Inventory only. No invented velocity VALUES. Teach Linear project cycle mapping, not a Jira or Asana 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 Project Cycle Map from Issue Inventory (No Invented Cycle Velocity) - Result

Examples

Example Input

Inventory: project Harbor Quay Onboarding as pasted issue cue HQ-214 Invite Flow as pasted state notes In Progress as pasted; project River Ops Billing as pasted issue cue RO-88 Invoice PDF as pasted. Velocity invent NONE. Point invent NONE.
Version: Linear Cycles 2025 as pasted (do not invent unreleased AI triage writer)
Workspace: Harbor Quay product team as pasted
SpecNames: Onboarding cycle map as pasted; Billing cycle map as pasted. Assignee email UNKNOWN.
ProjectCues: Onboarding as pasted; Billing as pasted. Mobile App UNKNOWN.
IssueCues: HQ-214 Invite Flow as pasted; RO-88 Invoice PDF as pasted. HQ-301 SSO UNKNOWN.
StateNotes: In Progress as pasted. Cycle velocity VALUES NOT IN INPUTS.
Banned: guaranteed velocity, velocity invent, point invent, email invent
Never: invent cycle velocity, invent estimate points, invent assignee emails, invent private URLs
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: project Harbor Quay Onboarding issue cue HQ-214 Invite Flow state notes In Progress; project River Ops Billing issue cue RO-88 Invoice PDF. Velocity invent NONE. Point invent NONE. Version Linear Cycles 2025. Workspace Harbor Quay product team. SpecNames Onboarding cycle map; Billing cycle map; Assignee email UNKNOWN. ProjectCues Onboarding; Billing; Mobile App UNKNOWN. IssueCues HQ-214 Invite Flow; RO-88 Invoice PDF; HQ-301 SSO UNKNOWN. StateNotes In Progress; Cycle velocity VALUES NOT IN INPUTS. Lang English. Banner: not a Linear billing estimate; not a sprint velocity certificate. Forbidden: invented cycle velocity, estimate points, assignee emails, private URLs, guaranteed velocity, velocity invent, point invent, email invent.

3. Spec name set. Onboarding cycle map; Billing cycle map as SpecNames. Assignee email UNKNOWN so write assignee email NOT IN INPUTS. No velocity VALUES beyond Inventory. No third project invented.

4. Version lock. Linear Cycles 2025 as pasted. Unreleased AI triage writer not used. Private URL packs NOT IN INPUTS.

5. Refuse. Velocity invent: refused. Point invent: refused. Email invent: refused. Private URL invent: refused. Guaranteed velocity: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: assignee email policy, Mobile App ProjectCues, HQ-301 SSO IssueCues, velocity VALUES StateNotes, cycle dates 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.