Productivity

GitHub Projects v2 from a Workflow Brief (No Invented Assignees)

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.

0.0
0Reviews
P
August 28, 2026

Prompt

Act as a GitHub Projects v2 board designer who only uses a pasted workflow brief. You define fields, views, and status options. You do not invent assignees, labels, or repository names. This is not a Jira epic breakdown, not a Linear template pack, and not a GitHub Actions matrix.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- 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]

Generate:
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.

Constraints:
- 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.

Instructions

Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.

Examples

Example Input

Brief: intake bugs and small features for a docs site; stages triage then in progress then review then done; WIP soft cap 3 in progress; item types bug and chore only as pasted
Statuses: Triage, In Progress, Review, Done
Fields: Priority (P1/P2/P3), Type (bug/chore)
Views: Board by Status; Table sorted by Priority
Banned: @alice invent, label urgent invent, repo acme/docs invent
Never: invent assignees, invent labels, invent repo names, invent Jira epic keys
Format: ledger + purpose + fields + views + refuse + gaps
Lang: English
Repo: UNKNOWN
Assignees: NONE

Example Output

1. Ledger. Workflow: docs-site bugs and small features; stages Triage, In Progress, Review, Done; WIP soft cap 3 in progress; types bug and chore. Statuses as pasted. Fields Priority P1/P2/P3, Type bug/chore. Views Board by Status; Table by Priority. Repo UNKNOWN. Assignees NONE. Lang English. Forbidden: @alice invent, label urgent invent, repo acme/docs invent, invent assignees, invent labels, invent repo names, invent Jira epic keys.

2. Purpose. A GitHub Projects v2 board to move docs-site bugs and chores from triage through review to done with a soft WIP of 3 in progress.

3. Status options. Triage | In Progress | Review | Done.

4. Custom fields.
- Priority: single select P1, P2, P3 as pasted.
- Type: single select bug, chore as pasted.
No other fields (NONE beyond Fields list).

5. Views.
- Board by Status: columns Triage, In Progress, Review, Done; show Type and Priority on cards.
- Table sorted by Priority: rows filterable by Type; sort Priority then Status.
WIP note: soft cap 3 items in In Progress from Brief (enforcement automation NOT IN INPUTS).

6. Repo. REPO UNKNOWN. Assignees. NO ASSIGNEES.

7. Refuse. @alice invent refused. Label urgent invent refused. Repo acme/docs invent refused. Jira epic breakdown refused. Linear template pack refused. GitHub Actions matrix YAML refused.

8. Compliance. Banned hits quoted and cut: @alice invent; label urgent invent; repo acme/docs invent. Format ledger+purpose+fields+views+refuse+gaps. Gaps: repo full name, whether Issues vs Drafts, iteration field Y/N, automation for WIP, default Priority.

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.

Reviews (0)

Please login to leave a review.
Loading reviews...