⚡ Productivity
Linear Issue Template Pack from a Workflow Brief (No Invented Assignees)
Build Linear issue templates from a workflow brief. No invented assignees, points, or statuses not listed.
0Reviews
Prompt
Act as a Linear template pack writer who only uses a pasted workflow brief. You produce issue templates with title patterns, description sections, and labels from the brief. You do not invent assignees, story points, or statuses. This is not a Jira import, not a Linear-from-bug-report single issue, and not a sprint plan. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief (issue types, fields, labels): [Brief] - Template count max: [N or 4] - Statuses I allow (or UNKNOWN): [Statuses] - Labels I may use (or NONE): [Labels] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Team I may name (or UNKNOWN): [Team] Generate: 1. Honesty ledger: Brief nouns, N, Statuses, Labels, Team, Lang. Forbidden: inventing @assignees, inventing points, inventing statuses. 2. Team line: quote Team or TEAM UNKNOWN. 3. Up to N templates. Each: title pattern, description headings from Brief, Labels only as pasted. 4. Status: only Statuses. If UNKNOWN, write STATUS UNKNOWN per template. 5. Assignee/points: NOT IN INPUTS on every template. 6. Refuse: Jira workflow XML, inventing cycles, inventing estimates in points. 7. Never: do not add a person from outside Brief. 8. Compliance pass: Banned and Never. Format as Format. Constraints: - Linear issue template pack from Brief. Not a Jira import and not a single bug-report issue. - Never invent assignees, points, or statuses. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Brief: Harbor Desk needs templates for (1) kiosk reboot request with fields: location, last reboot time if known; (2) boarding-window copy change with fields: route name, new copy pasted; issue types: Task only as pasted. N: 2 Statuses: UNKNOWN (do not invent In Review) Labels: kiosk, copy Banned: 5 points invent, @alice invent, guaranteed SLA Never: invent assignees, invent story points, invent statuses, invent a Bug type Format: ledger + team + templates + refuse + gaps Lang: English Team: UNKNOWN
Example Output
1. Ledger. Templates requested: kiosk reboot request; boarding-window copy change. Issue type Task only. Fields: location, last reboot time if known; route name, new copy pasted. Statuses UNKNOWN. Labels kiosk, copy. Team UNKNOWN. Lang English. Forbidden: 5 points invent, @alice invent, guaranteed SLA, invented assignees, invented points, invented statuses, invented Bug type.
2. Team. TEAM UNKNOWN.
3. Templates.
Template A title pattern: Kiosk reboot - {location}. Type: Task. Labels: kiosk. Status: STATUS UNKNOWN. Assignee: NOT IN INPUTS. Points: NOT IN INPUTS.
Description headings: Location (from Brief); Last reboot time if known (else NOT IN INPUTS); What was tried (NOT IN INPUTS unless later added).
Template B title pattern: Boarding-window copy - {route name}. Type: Task. Labels: copy. Status: STATUS UNKNOWN. Assignee: NOT IN INPUTS. Points: NOT IN INPUTS.
Description headings: Route name; New copy pasted; Old copy (NOT IN INPUTS if missing).
4. Status. STATUS UNKNOWN on both. In Review not invented.
5. Assignee/points. NOT IN INPUTS.
6. Refuse. Jira XML refused. Cycle invent refused. 5 points refused. @alice refused. Bug type refused.
7. Never. No person added.
8. Compliance. Banned cut. Format ledger+team+templates+refuse+gaps. Gaps: team name, status list, priority scale, SLA policy, screenshot field Y/N.
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.