How to Build a Linear Issue Template from a Workflow Brief
Issue templates invent assignees. Leave people and points UNKNOWN.
The matching generator is the Linear Issue Template 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).
Lock the team key
Build a Linear issue template from a workflow brief. Never invent assignees, estimate points, or project IDs. 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: [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]
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.
Labels only from the allowlist
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, Team, Labels policy, Lang, Max. Forbidden: invented assignees, invented points, invented project UUIDs.
- Workflow map: intake -> build -> review from Brief.
- Template: title pattern; up to Max description sections; labels only from Labels or NONE.
- Field policy: assignee UNKNOWN; estimate UNKNOWN unless Brief provides numbers.
- Refuse list: invented @users, invented cycles, invented SLAs.
- Diff notes: Banned/Never cuts.
- Team note: UNKNOWN if blank.
- Compliance pass: Banned/Never hits. Section count vs Max. Gaps list of five. 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.
Refuse invented project UUIDs
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 template from Brief only. Not GitHub Projects and not Jira automation.
- Never invent assignees, points, or project IDs.
- Honor Max sections.
- 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.
Keep estimate UNKNOWN
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, no invented assignees, linear workflow template) 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.