Productivity

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

Turn a Linear team inventory into a cycle issue triage and priority map only. No invented velocity points, cycle times, or burnout scores beyond the inventory.

0.0
0Reviews
P
September 17, 2026

Prompt

Act as a Linear cycle issue triage cartographer who only uses a pasted team inventory. You write a cycle issue triage and priority map the inventory already supports. You do not invent velocity points, cycle times, burnout scores, or workspace credential secrets not in Inputs. This is not a Linear billing estimate and 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:
- Team inventory I lock (issue stubs, priority cues, cycle notes): [Inventory]
- Linear / workspace version notes I lock: [Version]
- Team or project label I may quote (or UNKNOWN): [Workspace]
- Required issue or cycle names I may quote (or UNKNOWN): [SpecNames]
- Issue names already present (or UNKNOWN): [IssueCues]
- Priority labels already present (or UNKNOWN): [PriorityCues]
- Cycle and label notes already present (or UNKNOWN): [CycleNotes]
- Words I must not use: [Banned]
- What I must never invent (velocity points, cycle times, burnout scores, workspace secrets): [Never]
- Output format: [Format]
- Language: [Lang]

Generate:
1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, IssueCues, PriorityCues, CycleNotes, Lang. Forbidden: invented velocity points, cycle times, burnout scores, workspace secrets. Banner: not a Linear billing estimate; not a delivery guarantee.
2. Cycle issue triage map: one numbered row per Inventory issue stub or priority cue. Missing CycleNotes write NOT IN INPUTS. Use Linear Issue, Cycle, Priority, Label, and Project language when Inventory supports it. Never print velocity-point or cycle-time VALUES not in Inventory.
3. Spec name set: only names in SpecNames. Unnamed issues stay NOT IN INPUTS. Never invent burnout 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 cycle times, inventing burnout scores, inventing workspace 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 cycle issue triage maps, not a Jira or Height 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 Cycle Issue Triage Map from Team Inventory (No Invented Velocity Points) - Result

Examples

Example Input

Inventory: issue Harbor Quay auth bug as pasted priority cue Urgent as pasted cycle notes Cycle 12 as pasted; issue River Ops docs gap as pasted priority cue Medium as pasted. Velocity invent NONE. Cycle invent NONE.
Version: Linear workspace current as pasted (do not invent unreleased AI triage pack)
Workspace: Harbor Quay platform team as pasted
SpecNames: auth bug triage map as pasted; docs gap priority map as pasted. Burnout UNKNOWN.
IssueCues: auth bug as pasted; docs gap as pasted. onboarding UNKNOWN.
PriorityCues: Urgent as pasted; Medium as pasted. Low UNKNOWN.
CycleNotes: Cycle 12 as pasted. Velocity VALUES NOT IN INPUTS.
Banned: guaranteed ship, velocity invent, cycle invent, secret invent
Never: invent velocity points, invent cycle times, invent burnout scores, invent workspace secrets
Format: ledger + table + specs + version + refuse + compliance
Lang: English

Example Output

1. Ledger. Inventory: issue Harbor Quay auth bug priority cue Urgent cycle notes Cycle 12; issue River Ops docs gap priority cue Medium. Velocity invent NONE. Cycle invent NONE. Version Linear workspace current. Workspace Harbor Quay platform team. SpecNames auth bug triage map; docs gap priority map; Burnout UNKNOWN. IssueCues auth bug; docs gap; onboarding UNKNOWN. PriorityCues Urgent; Medium; Low UNKNOWN. CycleNotes Cycle 12; Velocity VALUES NOT IN INPUTS. Lang English. Banner: not a Linear billing estimate; not a delivery guarantee. Forbidden: invented velocity points, cycle times, burnout scores, workspace secrets, guaranteed ship, velocity invent, cycle invent, secret invent.

2. Cycle issue triage map.
1. Harbor Quay auth bug | IssueCues auth bug as pasted | PriorityCues Urgent as pasted | CycleNotes Cycle 12 as pasted | velocity VALUES NONE | cycle NONE | Linear cycle issue triage map only.
2. River Ops docs gap | IssueCues docs gap as pasted | PriorityCues Medium as pasted | CycleNotes beyond Cycle 12 NOT IN INPUTS | velocity VALUES NONE | cycle NONE.
Burnout UNKNOWN so write burnout VALUES NOT IN INPUTS. onboarding not invented beyond IssueCues.

3. Spec name set. auth bug triage map; docs gap priority map as SpecNames. Burnout UNKNOWN so write burnout VALUES NOT IN INPUTS. No velocity VALUES beyond Inventory. No third issue invented.

4. Version lock. Linear workspace current as pasted. Unreleased AI triage pack not used. Low PriorityCues NOT IN INPUTS.

5. Refuse. Velocity invent: refused. Cycle invent: refused. Burnout invent: refused. Secret invent: refused. Guaranteed ship: refused.

6. Compliance. Banned hits none. Format ledger+table+specs+version+refuse+compliance. Gaps: burnout policy, onboarding IssueCues, Low PriorityCues, velocity VALUES CycleNotes, label list 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.

Reviews (0)

Please login to leave a review.
Loading reviews...