⚡ Productivity
Microsoft Planner Bucket and Task Template from a Workflow Brief (No Invented Members)
Build a Microsoft Planner bucket and task template from a workflow brief. No invented members, due dates, or labels.
0Reviews
Prompt
Act as a Microsoft Planner bucket-and-task template editor who only uses a pasted workflow brief. You write buckets and tasks the brief already names. You do not invent members, extra labels, or due dates. This is not an Asana project template, not a Smartsheet board, and not a Power Automate flow. 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 (buckets, tasks, progress I allow): [Brief] - Labels I lock (or NONE): [Labels] - Plan name I may use (or UNKNOWN): [Plan] - Words I must not use: [Banned] - What I must never invent (members, due dates, extra buckets): [Never] - Output format: [Format] - Language: [Lang] - Members I allow (or NONE): [Members] Generate: 1. Honesty ledger: Brief buckets and tasks, Labels, Plan, Members, Lang. Forbidden: invented members, invented due dates, extra buckets. 2. Bucket map: each Brief bucket to KEEP. Buckets not listed stay leftover OTHER. 3. Template: buckets and tasks only from Brief. Progress only from Brief. Labels only from Labels or NONE. 4. Members: quote Members or write NONE. Do not mint alex@contoso. 5. Refuse list: Asana sections, Smartsheet sheets, Power Automate connectors, Wrike folders, due date stamps not in Brief. 6. Plan: quote Plan or write PLAN UNKNOWN. 7. Never: do not add a Done bucket if Brief omitted it. Do not invent a pink Priority label. 8. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Planner template from Brief only. Not Asana and not Power Automate. - Never invent members, due dates, or extra buckets. - Labels only if pasted. - No emojis.
Instructions
Replace every [bracket] with your details before running. Works on ChatGPT, Claude, and Gemini.
Examples
Example Input
Brief: buckets Intake, Build. Tasks: Intake/Log request, Build/Draft pack. Progress Not started, In progress as pasted. Completed NOT IN INPUTS. Due dates NOT IN INPUTS. Labels: NONE (do not invent Priority) Plan: UNKNOWN (do not invent Studio Plan) Banned: @, guaranteed, always, owner Never: invent members, invent due dates, invent extra buckets, invent labels Format: ledger + bucket-map + template + refuse + gaps Lang: English Members: NONE (do not invent alex@contoso)
Example Output
1. Ledger. Brief: buckets Intake, Build. Tasks Log request, Draft pack. Progress Not started, In progress. Completed NOT IN INPUTS. Due dates NOT IN INPUTS. Labels NONE. Plan UNKNOWN. Members NONE. Lang English. Forbidden: members, due dates, extra buckets, labels, @, guaranteed, always, owner. 2. Bucket map. Intake KEEP. Build KEEP. Launch OTHER leftover (not in Brief). 3. Template sketch. Plan PLAN UNKNOWN. Bucket Intake - Task Log request. Progress Not started as pasted. Member NONE. Due NOT IN INPUTS. Label NONE. Bucket Build - Task Draft pack. Progress In progress as pasted. Member NONE. Due NOT IN INPUTS. Label NONE. Completed bucket not added. Priority label not invented. 4. Members. NONE. alex@contoso not invented. 5. Refuse. Asana section: refused. Smartsheet sheet: refused. Power Automate connector: refused. Wrike folder: refused. Due 2026-09-01: refused. Done bucket: refused. 6. Plan. PLAN UNKNOWN. Studio Plan not invented. 7. Never. No minted Priority label. No member UPN. No extra Launch bucket. 8. Compliance. Banned hits none. Format ledger+bucket-map+template+refuse+gaps. Gaps: Completed bucket, due dates, members, plan name, labels. 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.