How to Build Linear Issue Templates from a Workflow Brief
Linear templates invent @assignees. Title patterns from the brief. STATUS UNKNOWN if blank.
The matching generator is the Linear Issue Template Pack from a Workflow Brief (No Invented Assignees) (Linear Issue Template Pack From A Workflow Brief No Invented Assignees) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Name the team or write TEAM UNKNOWN
Build Linear issue templates from a workflow brief. No invented assignees, points, or statuses not listed. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
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]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
Templates only for issue types in the brief
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Brief nouns, N, Statuses, Labels, Team, Lang. Forbidden: inventing @assignees, inventing points, inventing statuses.
- Team line: quote Team or TEAM UNKNOWN.
- Up to N templates. Each: title pattern, description headings from Brief, Labels only as pasted.
- Status: only Statuses. If UNKNOWN, write STATUS UNKNOWN per template.
- Assignee/points: NOT IN INPUTS on every template.
- Refuse: Jira workflow XML, inventing cycles, inventing estimates in points.
- Never: do not add a person from outside Brief.
- Compliance pass: Banned and Never. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Leave points and assignees NOT IN INPUTS
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- 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.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Refuse invented statuses and Jira XML
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (linear issue template pack, workflow brief linear templates, no invented assignees) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.