how would you rewrite my given human query to adapt it better for an AI query, show me…
- User
how would you rewrite my given human query to adapt it better for an AI query, show me your best 3 modifications, adaptations, clarifications
- Assistant
Below are three alternative ways you could phrase your request so an AI system (or any language model) instantly understands the context, constraints, and desired output. Each version:
• Establishes clear context
• Specifies the task in detail
• States formatting expectations
• Tells the AI how to “think” or structure its work
1️⃣ “Step-by-Step Expansion” Prompt
Earlier you decomposed our launch strategy into 155 tasks.
- Re-examine that list, break every multi-part bullet into truly atomic tasks (one action per line).
- Number each task sequentially.
- When finished, give me the final tally as “Total = X tasks” on its own line.
Think step-by-step and do not skip any implicit activities.
Why it works:
• Recaps prior output → gives the model context.
• Defines “atomic” clearly.
• Outlines a three-part structure.
• Adds a “think step-by-step” nudge for completeness.
2️⃣ “Exhaustive Checklist” Prompt
Please create the most exhaustive checklist possible of singular, non-overlapping tasks required to launch an AI-powered personal-assistant app.
• Cover product, security, marketing, PR, partnerships, analytics, support, legal, and post-launch growth.
• Each line = one verb-led task (e.g., “Draft privacy policy”).
• Group by functional area with sub-headings, but maintain one running numeric sequence.
• Conclude with a bold “Grand Total: __ tasks”.
Review silently before responding to ensure nothing is missing.Why it works:
• Eliminates ambiguity around scope.
• Specifies verb-led formatting.
• Keeps a single numbering sequence despite sub-groups.
• Requests a silent self-check (“review silently”) to encourage reflection.
3️⃣ “Audit & Augment” Prompt
Act as a launch-operations auditor.
- Copy the 200 tasks you produced earlier into a fresh list.
- Re-read the original launch strategy and identify every missing micro-task (e.g., “verify push-notification certificates”, “localize App Store screenshots”).
- Insert the new tasks in the correct functional sections, continuing the numbering.
- Highlight newly added tasks in italic.
- Output the updated list followed by a summary line:
• New tasks added: N
• Revised total tasks: M
Don’t re-explain the strategy—just the amended list and counts.
Why it works:
• Tells the model to audit (compare old vs. new).
• Makes insertion & formatting rules explicit.
• Provides a reporting structure for quick verification.
Pick whichever style matches your goals—each should yield a clearer, more AI-friendly response than the original, brief instruction “try another time, think longer.”
- User
Incorrect. my Complex Human Task: "Develop a comprehensive launch strategy for our new AI-powered personal assistant app"
- Assistant
Below are three “AI-ready” rewrites of your task.
Each version adds context, scope, formatting rules, and requested depth so the model knows exactly what to produce and how to present it.
1️⃣ Executive-Blueprint Prompt
You are a GTM strategist.
• Build a COMPLETE launch plan for a new AI-powered personal-assistant mobile app.
• Cover: product readiness, security/compliance, branding, pre-launch buzz, launch-day actions, paid/organic acquisition, partnerships, post-launch growth, KPIs, budget split, team roles, and risk mitigation.
• Organize by phase (Pre-Launch, Launch Week, Post-Launch) with sub-sections and bullet points.
• End with a one-page Gantt-style timeline and a table of success metrics.Why it helps: explicit audience (“GTM strategist”), exhaustive scope list, clear structure, and deliverable formats.
2️⃣ Investor-Deck Prompt
Draft a “launch strategy” slide deck outline (10–12 slides) for our upcoming AI personal-assistant app.
- Slide titles + 3–5 key bullets each.
- Must address: Market positioning, UVP vs. Siri/Google/Alexa, target personas, traction goals, marketing channels, budget ($ & %), 90-day roadmap, and measurable OKRs.
- Finish with a risks / contingencies slide.
Why it helps: constrains output to deck format—easy to drop into PowerPoint.
3️⃣ Task-Tracker Prompt
Produce an Asana-ready task list to launch an AI-powered personal-assistant app.
• Break down ALL work into atomic tasks (one verb + one object).
• Columns: “Task”, “Owner Role”, “Start Week”, “Duration (days)”, “Dependencies”.
• Group tasks under headings: Product, Security, Marketing, PR, Partnerships, Analytics, Support, Legal.
• Deliver in Markdown table; number every task; finish with “Total tasks: __”.Why it helps: directly creates a project-management import with clear ownership and sequencing.
- User
now list the three new prompts, no further explanation, just the prompts
- Assistant
-
You are a GTM strategist.
• Build a COMPLETE launch plan for a new AI-powered personal-assistant mobile app.
• Cover: product readiness, security/compliance, branding, pre-launch buzz, launch-day actions, paid/organic acquisition, partnerships, post-launch growth, KPIs, budget split, team roles, and risk mitigation.
• Organize by phase (Pre-Launch, Launch Week, Post-Launch) with sub-sections and bullet points.
• End with a one-page Gantt-style timeline and a table of success metrics. -
Draft a “launch strategy” slide deck outline (10–12 slides) for our upcoming AI personal-assistant app.
-
Slide titles + 3–5 key bullets each.
-
Must address: Market positioning, UVP vs. Siri/Google/Alexa, target personas, traction goals, marketing channels, budget ($ & %), 90-day roadmap, and measurable OKRs.
-
Finish with a risks / contingencies slide.
-
Produce an Asana-ready task list to launch an AI-powered personal-assistant app.
• Break down ALL work into atomic tasks (one verb + one object).
• Columns: “Task”, “Owner Role”, “Start Week”, “Duration (days)”, “Dependencies”.
• Group tasks under headings: Product, Security, Marketing, PR, Partnerships, Analytics, Support, Legal.
• Deliver in Markdown table; number every task; finish with “Total tasks: __”.
-
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.