⚡ Productivity

Asana Project Template from a Workflow Brief (No Invented Assignees)

Build an Asana project template from a workflow brief. No invented assignees, custom fields, or due dates.

0.0
0Reviews
P
August 29, 2026

Prompt

Act as an Asana project-template editor who only uses a pasted workflow brief. You write sections and tasks the brief already names. You do not invent assignees, extra custom fields, or due dates. This is not a Wrike folder tree, not a Smartsheet board, and not a RACI matrix dump.
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 (sections, tasks, statuses I allow): [Brief]
- Custom fields I lock (or NONE): [Fields]
- Workspace I may name (or UNKNOWN): [Workspace]
- Words I must not use: [Banned]
- What I must never invent (assignees, due dates, extra sections): [Never]
- Output format: [Format]
- Language: [Lang]
- Members I allow (or NONE): [Members]

Generate:
1. Honesty ledger: Brief sections and tasks, Fields, Workspace, Members, Lang. Forbidden: invented assignees, invented due dates, extra sections.
2. Section map: each Brief section to KEEP. Sections not listed stay leftover OTHER.
3. Template: sections and tasks only from Brief. Statuses only from Brief. Fields only from Fields or NONE.
4. Members: quote Members or write NONE. Do not mint @alex.
5. Refuse list: Wrike folder hierarchy, Smartsheet sheet, RACI matrix, Jira epic, due date stamps not in Brief.
6. Workspace: quote Workspace or write WORKSPACE UNKNOWN.
7. Never: do not add a Done status 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:
- Asana template from Brief only. Not Wrike and not a RACI dump.
- Never invent assignees, due dates, or extra sections.
- 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: sections Intake, Build. Tasks: Intake/Log request, Build/Draft pack. Statuses Open, Blocked as pasted. Done NOT IN INPUTS. Due dates NOT IN INPUTS.
Fields: NONE (do not invent Priority)
Workspace: UNKNOWN (do not invent Studio)
Banned: @, guaranteed, always, owner
Never: invent assignees, invent due dates, invent extra sections, invent custom fields
Format: ledger + section-map + template + refuse + gaps
Lang: English
Members: NONE (do not invent @alex)

Example Output

1. Ledger. Brief: sections Intake, Build. Tasks Log request, Draft pack. Statuses Open, Blocked. Done NOT IN INPUTS. Due dates NOT IN INPUTS. Fields NONE. Workspace UNKNOWN. Members NONE. Lang English. Forbidden: assignees, due dates, extra sections, custom fields, @, guaranteed, always, owner.

2. Section map. Intake KEEP. Build KEEP. Launch OTHER leftover (not in Brief).

3. Template sketch.
Project template from Brief. Workspace UNKNOWN.
Section Intake
- Task Log request. Status Open as pasted. Assignee NONE. Due NOT IN INPUTS.
Section Build
- Task Draft pack. Status Blocked as pasted. Assignee NONE. Due NOT IN INPUTS.
Custom fields NONE. Priority not invented. Done status not added.

4. Members. NONE. @alex not invented.

5. Refuse. Wrike folder tree: refused. Smartsheet board: refused. RACI matrix: refused. Jira epic: refused. Due 2026-09-01: refused. Done column: refused.

6. Workspace. WORKSPACE UNKNOWN. Studio not invented.

7. Never. No minted Priority field. No @assignee. No extra Launch section.

8. Compliance. Banned hits none. Format ledger+section-map+template+refuse+gaps. Gaps: Done status, due dates, members, workspace, 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...