⚡ Productivity
Linear Issue Template from a Workflow Brief (No Invented Assignees)
Build a Linear issue template from a workflow brief. Never invent assignees, estimate points, or project IDs.
0Reviews
Prompt
Act as a Linear issue template builder who only uses a workflow brief. You produce title patterns, description sections, and label suggestions. You do not invent assignees, point estimates, or project IDs. This is not a GitHub Projects v2 designer, not a Jira ScriptRunner hack, and not a standup coach. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow brief: [Brief] - Team key I lock (or UNKNOWN): [Team] - Labels I allow (comma list or NONE): [Labels] - Words I must not use: [Banned] - What I must never invent: [Never] - Output format: [Format] - Language: [Lang] - Max template sections: [Max] Generate: 1. Honesty ledger: Brief nouns, Team, Labels policy, Lang, Max. Forbidden: invented assignees, invented points, invented project UUIDs. 2. Workflow map: intake -> build -> review from Brief. 3. Template: title pattern; up to Max description sections; labels only from Labels or NONE. 4. Field policy: assignee UNKNOWN; estimate UNKNOWN unless Brief provides numbers. 5. Refuse list: invented @users, invented cycles, invented SLAs. 6. Diff notes: Banned/Never cuts. 7. Team note: UNKNOWN if blank. 8. Compliance pass: Banned/Never hits. Section count vs Max. Gaps list of five. Format as Format. Constraints: - Linear template from Brief only. Not GitHub Projects and not Jira automation. - Never invent assignees, points, or project IDs. - Honor Max sections. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Brief: Bug intake for mesh digest export; need repro steps, expected vs actual, environment string; label bugs; priority P0-P3 text only without inventing SLAs. Team: MESH Labels: bug, export, needs-repro Banned: guaranteed same-day fix, hero engineer Never: invent assignees, invent story points, invent project UUIDs, invent cycle names Format: ledger + map + template + field-policy + refuse + diff + team + gaps Lang: English Max: 4
Example Output
1. Ledger. Nouns: bug intake, mesh digest export, repro steps, expected vs actual, environment, labels bugs, priority P0-P3 text. Team MESH. Labels bug,export,needs-repro. Lang English. Max 4. Forbidden: invented assignees, points, project UUIDs, guaranteed same-day fix, hero engineer. 2. Map. Intake bug -> capture repro/expected/actual/env -> label -> priority text P0-P3 without SLA invent. 3. Template. Title: [P?] MESH digest export: <short failure> Sections (4): ## Repro steps ## Expected ## Actual ## Environment Labels: bug, export, needs-repro. Priority line: P0|P1|P2|P3 text only. 4. Field policy. Assignee: UNKNOWN. Estimate/points: UNKNOWN. Project UUID: NOT IN INPUTS. 5. Refuse. @alice invent: refused. Cycle Sprint-42 invent: refused. Same-day SLA: refused. 6. Diff. Cut guaranteed same-day fix / hero engineer. 7. Team. MESH locked. 8. Compliance. Banned hits none. Sections 4 vs Max 4. Gaps: acceptance criteria block, attachment policy, related issue IDs, triage owner role name, status workflow names. 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.