⚡ Productivity

Azure DevOps Work Item Template from a Workflow Brief (No Invented Assignees)

Build an Azure DevOps work-item template from a workflow brief. No invented assignees, states, or due dates.

0.0
0Reviews
P
August 29, 2026

Prompt

Act as an Azure DevOps work-item template editor who only uses a pasted workflow brief. You write work-item types, states, and fields the brief already names. You do not invent assignees, extra states, or due dates. This is not a Jira workflow, not an Asana project template, and not a GitHub Issues form.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.

Inputs:
- Workflow brief I lock (types, states, fields I allow): [Brief]
- Custom fields I lock (or NONE): [Fields]
- Project I may name (or UNKNOWN): [Project]
- Words I must not use: [Banned]
- What I must never invent (assignees, due dates, extra states): [Never]
- Output format: [Format]
- Language: [Lang]
- Members I allow (or NONE): [Members]

Generate:
1. Honesty ledger: Brief types and states, Fields, Project, Members, Lang. Forbidden: invented assignees, invented due dates, extra states.
2. State map: each Brief state to KEEP. States not listed stay leftover OTHER.
3. Template: work-item types and fields only from Brief. States only from Brief. Fields only from Fields or NONE.
4. Members: quote Members or write NONE. Do not mint @alex.
5. Refuse list: Jira workflow XML, Asana sections, GitHub issue forms, due date stamps not in Brief.
6. Project: quote Project or write PROJECT UNKNOWN.
7. Never: do not add a Closed state if Brief omitted it. Do not invent a custom field named Priority.
8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format.

Constraints:
- Azure DevOps work-item template from Brief only. Not Jira and not Asana.
- Never invent assignees, due dates, or extra states.
- Fields only if pasted.
- No emojis.

Instructions

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

Examples

Example Input

Brief: type User Story as pasted; states New, Active as pasted. Fields Title, Description as pasted. Closed NOT IN INPUTS. Due dates NOT IN INPUTS.
Fields: NONE extra (do not invent Priority)
Project: UNKNOWN (do not invent Studio)
Banned: @, guaranteed, always, owner
Never: invent assignees, invent due dates, invent extra states, invent custom fields
Format: ledger + state-map + template + refuse + gaps
Lang: English
Members: NONE (do not invent @alex)

Example Output

1. Ledger. Brief: type User Story; states New, Active; fields Title, Description. Closed NOT IN INPUTS. Due dates NOT IN INPUTS. Extra Fields NONE. Project UNKNOWN. Members NONE. Lang English. Forbidden: assignees, due dates, extra states, custom fields, @, guaranteed, always, owner.

2. State map. New KEEP. Active KEEP. Closed OTHER leftover (not in Brief).

3. Template sketch.
Process template from Brief. Project UNKNOWN.
Work item type User Story as pasted.
- Field Title as pasted. Assignee NONE. Due NOT IN INPUTS.
- Field Description as pasted. Assignee NONE. Due NOT IN INPUTS.
States New, Active as pasted. Closed not added. Priority not invented.

4. Members. NONE. @alex not invented.

5. Refuse. Jira workflow XML: refused. Asana section: refused. GitHub issue form: refused. Due 2026-09-01: refused. Closed state: refused.

6. Project. PROJECT UNKNOWN. Studio not invented.

7. Never. No minted Priority field. No @assignee. No extra Closed state.

8. Compliance. Banned hits none. Format ledger+state-map+template+refuse+gaps. Gaps: Closed state, due dates, members, project name, extra custom fields.

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