Home/Blog/How to Design GitHub Projects v2 from a Workflow Brief
Blog

How to Design GitHub Projects v2 from a Workflow Brief

P
promptstudio
How to Design GitHub Projects v2 from a Workflow Brief

Projects v2 boards invent assignees. Fields and views from the brief. Not Jira. Not Actions.

The matching generator is the GitHub Projects v2 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).

List custom fields from the brief

Design a GitHub Projects v2 board (fields, views, status options) from a workflow brief. No invented assignees, labels, or repo names. Not Jira epics, not Linear templates, not Actions matrix. 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 (stages, item types, WIP notes): [Brief]
Status options I allow: [Statuses]
Custom fields I allow (or NONE): [Fields]
Views I allow (or NONE): [Views]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Repo name (or UNKNOWN): [Repo]
Assignees policy (NONE): [Assignees]

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.

Define views without invented filters

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:

  1. Honesty ledger: Brief, Statuses, Fields, Views, Repo, Assignees, Lang.
  2. Project purpose one-liner from Brief.
  3. Status field options exactly as Statuses.
  4. Custom fields: only Fields or NONE.
  5. Views: only Views or NONE; describe filters using Brief nouns only.
  6. Repo: if UNKNOWN write REPO UNKNOWN. Assignees: if NONE write NO ASSIGNEES.
  7. Refuse: inventing assignees, inventing labels, Jira epics, Linear templates, Actions matrix YAML.
  8. Compliance pass: Banned and Never. Format as Format. Gaps list of five.

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 assignees NONE

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:

  • GitHub Projects v2 schema from Brief only. No invented assignees.
  • Never invent repo names or labels not pasted.
  • Not Jira, Linear, or Actions matrix.
  • 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 Jira and Actions padding

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 (github projects v2 schema, projects v2 from workflow, 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.