Prompt feed built for modern teams.

Create a 1-day plan for {{role}}. Ask for my top 3 outcomes, then build a time-blocked schedule with 50-minute focus blocks, 10-minute breaks, one buffer, and one recovery block. Keep to 120 words and return as a checklist.

Give me a quick priority score for a list of tasks using impact (1–5), effort (1–5), urgency (1–5), and risk (1–5). Return a table sorted by highest score with a one-line action recommendation per task. Tasks: {{list}}

Convert this meeting idea into an async doc plan. Include: purpose, needed inputs, owner, reviewers, due date, decision format, and a 5-question comment prompt. Keep under 110 words. Meeting context: {{details}}

Design a 3-bucket email triage rule set (Do now, Delegate, Defer) for {{role}}. Give criteria, canned subject tags, and a 2-sentence reply template for each bucket. Keep it under 120 words.

Plan a 90-minute deep work session for {{task}}. Include: clear finish line, 3 checkpoints, distraction blockers, and a 3-minute reset ritual. Deliver as a numbered list under 110 words.

Write a 20-minute weekly review for {{role}}. Sections: wins, misses, surprises, blockers, decisions made, decisions pending, top 5 for next week. Include 3 reflection questions. Keep it under 130 words.

Craft a standup update that is crisp and outcome-based. Format: Yesterday (outcomes), Today (one measurable goal), Risks (with mitigation), Help needed. Keep under 70 words. Context: {{notes}}

Turn this task into a delegation brief with objective, constraints, done definition, stakeholders, deadlines, and decision rights. Keep under 120 words. Task: {{task}}

After an interruption, help me restart in 3 minutes. Ask what I was doing, next visible action, and potential blocker. Return a micro-plan with the very next keystroke and a 30-minute focus block. Keep to 80 words.

Run a 10-minute postmortem for a small issue. Sections: timeline, root cause (5 Whys), impact, what went well, what to change (max 3), next owner. Keep under 130 words. Incident: {{summary}}

Review my weekly calendar and propose deletions, async replacements, and mergers. Summarize as: Remove, Make Async, Shorten, Keep. Give 1 sentence per item. Calendar notes: {{paste}}

Given tasks and past estimates vs actuals, recalibrate. Return a table: Task, Past Estimate, Actual, New Estimate, Risk Note. Keep within 100 words. Data: {{details}}

Ask for my blocker, then propose 3 ways to unblock in under 30 minutes, plus 1 longer-term fix. Keep to 80 words. Blocker: {{issue}}

Design a 7-day habit tracker for {{habit}} with a daily 2-minute reflection question, a trigger, and a reward. Keep under 90 words.

Convert this decision into a log entry: context, options considered, chosen option, rationale, date, owner, and review date. Keep to 90 words. Decision: {{details}}

Create a workback plan from deadline {{date}} for {{deliverable}}. Include milestones, owners, risks, and buffers. Keep to 120 words and deliver as bullets.

Suggest a 3-block focus routine (body, environment, mindset) for {{task}}. Include music/ambient suggestions, lighting, and a one-line mantra. Keep to 80 words.

Draft a 30-minute 1:1 agenda for {{manager/peer}} focused on outcomes and roadblocks. Include 5 questions and 2 commitments to confirm. Keep under 90 words.

Summarize these meeting notes into decisions, owners, and next deadlines. Keep under 120 words and list open questions. Notes: {{paste}}

Design a 3-cycle Pomodoro variant for {{task}}: focus length, break length, focus target, and small reward. Keep to 70 words.

Create an escalation ladder for when a task is stuck. Levels: self-help, peer, manager, leadership. Provide triggers, expected response time, and message template for each. Keep under 120 words.

Build a realistic work plan for a travel day with 3 micro-tasks, 1 async update, and 1 buffer. Include tips for offline prep. Keep to 90 words. Context: {{details}}

Turn raw notes into a crisp status update with: current state, last 2 wins, top risk, next milestone, ask. Keep under 80 words. Notes: {{paste}}

Audit my past week for energy peaks/dips. Ask for schedule, then suggest a 3-block day structure and 2 habits to protect high-energy slots. Keep to 120 words.

Help me start a dreaded task. Break it into a 5-minute starter action, 20-minute main action, and a reward. Provide a short script to begin. Keep under 70 words. Task: {{task}}

Create a template to capture daily wins: What happened, Evidence, Impact, Next step. Include 3 prompts to surface quiet wins. Keep to 80 words.

Guide me through a 30-minute inbox zero sprint: filters, batch replies, snooze rules, archive decisions. Provide 2 canned responses. Keep under 100 words.

Generate a context pack for {{project}} with: goal, constraints, stakeholders, dependencies, decision cadence, and preferred format. Keep to 110 words.

Write a short scope agreement for {{deliverable}}: in-scope, out-of-scope, definition of done, risks, and review date. Keep under 90 words.

Summarize the coming week: 3 outcomes, must-do meetings, big risks, buffers, and a short pep note. Keep under 90 words. Inputs: {{details}}

Rewrite this text into the target tone (choose: concise, warm, bold, academic, playful). Keep sentences under 18 words, remove filler, and keep it under 140 words. Text: {{paste}}

Condense this document into an executive summary: goal, key facts, decision needed, risks, next step. Limit to 120 words. Content: {{paste}}

Create a 5-beat story arc for {{topic}} using Setup, Tension, Turning Point, Resolution, CTA. Return as bullet outline under 120 words.

Turn these data points into a narrative paragraph with one clear takeaway and one action. Keep to 90 words. Data: {{paste}}

Rewrite the text to a 6th-grade reading level without losing accuracy. Use short sentences and everyday words. Keep under 120 words. Text: {{paste}}

Generate 6 headlines for {{offer}}. Mix formats: outcome-first, question, number, how-to, contrast, and curiosity. Keep each under 12 words.

Suggest 5 strong calls-to-action for {{page}}. Include one urgency angle, one value-first, one social proof, one risk-reversal, one curiosity. Keep each under 10 words.

Proofread the text and list fixes with reasons. Return as: Original, Fix, Rationale. Keep under 120 words. Text: {{paste}}

Insert these customer quotes into a cohesive paragraph that highlights pains, desired outcomes, and one promise. Keep under 100 words. Quotes: {{paste}}

Create 7 FAQs for {{product}}. Each answer under 30 words, focused on clarity and next step. Avoid jargon.

Write 3 bio options for {{platform}}. Formats: authoritative, friendly, crisp. Max 140 characters each. Include 1 proof point and 1 CTA link placeholder.

Draft a bridge paragraph that transitions from problem to solution for {{topic}}. Include 1 empathy line and 1 preview of the solution. Keep under 80 words.

Rewrite the text with line breaks after each sentence, bold the verbs, and keep sentences under 14 words. Limit to 120 words. Text: {{paste}}

Improve this email to be brief and kind. Structure: Greeting, 2-sentence body, single ask, sign-off. Keep under 90 words. Email: {{paste}}

Generate 3 analogies to explain {{concept}} to a beginner. Each under 20 words and reference familiar objects or daily life.

Expand these bullets into a short paragraph while keeping the same order and meaning. Keep to 110 words. Bullets: {{paste}}

Polish this microcopy for clarity and brevity. Return variants for button (<=14 chars), helper text (<=18 words), and tooltip (<=14 words). Copy: {{paste}}

Outline a case study: client, challenge, stakes, approach, results, quote, CTA. Keep under 130 words. Context: {{details}}

Draft a concise policy for {{topic}} with purpose, scope, definitions, rules, and enforcement. Keep under 150 words.

Summarize a mini style guide: tone words, banned phrases, preferred structures, and examples for openings/closings. Keep under 140 words. Brand: {{details}}

Create a detailed outline for a 1,200-word article on {{topic}}. Include working title, angle, 6–8 H2/H3s, and a takeaway per section. Keep under 150 words.

Rewrite the text with bolded keywords, short sentences, and a TL;DR at top. Keep under 140 words. Text: {{paste}}

Add persuasive framing to this copy using one credibility proof, one risk reversal, and one clear promise. Keep under 120 words. Copy: {{paste}}

Convert this policy into 8 FAQs with clear answers under 25 words. Keep reading level simple. Policy: {{paste}}

Write a concise changelog entry for {{feature}}. Include what changed, why it matters, and how to enable it. Keep under 90 words.

Clean this transcript by removing filler, correcting grammar, and keeping speaker labels. Keep length similar. Transcript: {{paste}}

Rewrite slide copy to fit 5x5 rule (5 lines, 5 words each max). Keep main message and include one optional presenter note. Text: {{paste}}

Expand this 1-line bio into a 120-word profile including role, impact, notable project, and personal touch. Bio: {{paste}}

Perform a line edit: tighten verbs, cut repetition, fix rhythm. Return the revised text and a 3-bullet rationale. Keep under 180 words total. Text: {{paste}}

Rewrite this message about a sensitive topic to be empathetic and precise. Include one validation line and one actionable next step. Keep under 120 words. Text: {{paste}}

Create an ICP snapshot: industry, size, roles, pains, desired outcomes, triggers, and buying objections. Keep under 140 words. Product: {{details}}

Write a positioning statement for {{product}} using: For [audience] who [pain], our product is [category] that [promise], unlike [alternative] it [differentiator]. Keep under 60 words.

Build a messaging grid for a launch with pillars, proof points, and sample lines for email, landing, and social. Keep under 180 words. Feature: {{details}}

Draft a campaign brief: objective, audience, core message, channels, budget guardrails, success metrics, timeline. Keep under 160 words. Campaign goal: {{goal}}

Create 5 ad copy variations for {{offer}} with one hook each: number, fear-of-missing, social proof, bold promise, and curiosity. Keep each under 20 words.

Distill the top 3 value props for {{product}} with a proof point and metric for each. Keep under 110 words.

Design a 5-email nurture flow: subject, angle, CTA, and send gap. Stages: welcome, problem framing, proof, offer, objection answer. Keep under 180 words.

Propose a 4-week content calendar for {{audience}} with 3 posts per week. Include format (video, carousel, blog), hook, and CTA. Keep under 180 words.

Outline a landing page: hero, proof, pains, outcomes, feature highlights, social proof, pricing, FAQ, CTA. Provide copy prompts for each block. Keep under 170 words. Offer: {{details}}

Draft a webinar plan: topic, title, agenda, demo flow, attendee promises, follow-up offer, and 3 audience questions. Keep under 170 words. Topic: {{topic}}

Write a partnership pitch email: shared audience insight, mutual value, simple next step, and suggested meeting times. Keep under 120 words. Partner: {{name}}

Teardown a competitor page: headline, promise, proof, CTA, pricing, differentiation. Provide 3 counter-messaging ideas. Keep under 180 words. URL summary: {{paste}}

Design a 4-email retention series for inactive users: reminder, value recap, success story, comeback offer. Include subject and CTA. Keep under 160 words. Product: {{product}}

Suggest 7 lead magnet ideas for {{audience}}. Mix checklists, calculators, templates, and short guides. Keep each idea under 18 words.

Create an ABM one-pager outline: account insight, tailored problem framing, custom proof, relevant feature, and tailored CTA. Keep under 150 words. Account: {{details}}

Write a 3-line booth opener, 3 qualifying questions, and a 2-line demo pitch for {{product}}. Keep under 90 words.

Craft pricing page copy for 3 tiers: persona fit, key features, reassurance bullet, and CTA. Keep under 160 words. Product: {{details}}

Turn these metrics into proof points with a short headline, number, and 1-line context. Keep under 120 words. Metrics: {{paste}}

Draft a referral request email: gratitude line, ideal referral description, easy way to connect, and a thank-you. Keep under 90 words.

Create a reactivation offer for churned users with a concise reason to return, incentive, and 2-step re-onboarding. Keep under 120 words. Product: {{product}}

Map lifecycle stages (signup, activation, habit, expansion) to 2 messages each: trigger, copy idea, CTA. Keep under 190 words. Product: {{details}}

Design a 6-question survey to understand {{goal}}. Mix multiple choice and open text. Add one segmentation question. Keep under 120 words.

Plan a refresh for this article: add sections, update stats, swap CTA, improve intro. Provide checklist under 130 words. Article summary: {{paste}}

Outline a 7-minute narrative demo: protagonist, problem, aha, key features, proof, CTA. Include time stamps. Keep under 160 words. Product: {{product}}

Draft a press pitch: news hook, why it matters, 2 data points, spokesperson, and clear next step. Keep under 130 words. Announcement: {{details}}

Create a case study brief: customer profile, challenge, solution, measurable results, quote, CTA. Keep under 150 words. Customer: {{details}}

Design an A/B test for copy: hypothesis, variant description, success metric, sample size note, and rollout rule. Keep under 120 words. Page: {{page}}

Summarize brand voice: 3 do's, 3 don'ts, 3 sample lines, and keywords to emphasize. Keep under 140 words. Brand: {{details}}

Adapt this web copy for {{locale}}. Keep message consistent, adjust idioms, and suggest localized proof points. Keep under 150 words. Copy: {{paste}}

Write a 4-step outbound sequence with subject lines, short bodies, and asks. Steps: intro, value, proof, close. Keep under 180 words. Persona: {{details}}

Given a diff summary, create a code review checklist: correctness, readability, edge cases, security, performance, and tests. Keep under 140 words. Diff: {{paste}}

Draft steps to reproduce a bug from this report. Include environment, setup, exact actions, expected vs actual, and logging to collect. Keep under 140 words. Report: {{paste}}

Create a lightweight test plan for {{feature}}. Include happy path, edge cases, failure cases, and data setup. Keep under 150 words.

Outline a refactor plan for {{area}}. Include goals, risks, safety checks, sequencing, and rollback plan. Keep under 150 words.

Draft an API contract: endpoint, method, request schema, response schema, error codes, and examples. Keep under 180 words. Purpose: {{details}}

Write concise docstrings for these functions including purpose, inputs, outputs, and edge cases. Keep each under 30 words. Code: {{paste}}

Assess time/space complexity of these functions and suggest simpler alternatives if needed. Keep under 150 words. Code: {{paste}}

Identify security risks in this snippet (inputs, auth, secrets, data handling). Provide fixes with specific patterns to apply. Keep under 170 words. Code: {{paste}}

Build a reading guide for this legacy file: what it does, key functions, risky areas, and 3 questions to confirm before editing. Keep under 150 words. File summary: {{paste}}

Rewrite these error messages to be actionable. Include cause hint, next step, and link placeholder. Keep each under 18 words. Errors: {{paste}}

Create a logging plan for {{feature}} with key events, levels, fields to capture, and redaction rules. Keep under 160 words.

Outline how to profile {{area}}. Include tools, metrics to watch, reproduction steps, and a success criterion. Keep under 150 words.

Prioritize tech debt items using impact, likelihood of failure, user reach, and fix effort. Return a ranked list with 1-line rationale each. Items: {{paste}}

Create an on-call handoff note: current incidents, flaky areas, top alerts, runbooks, and watch-outs. Keep under 130 words. Context: {{details}}

Draft a runbook outline for {{problem}}: symptoms, quick checks, remediation steps, rollback, and who to ping. Keep under 150 words.

Review this schema proposal for normalization, indexing, growth risks, and naming. Provide 5 improvement bullets. Keep under 170 words. Schema: {{paste}}

Outline a safe migration for {{change}} with phases, backfill approach, verification, and rollback plan. Keep under 180 words.

Plan a hotfix: scope, quick diagnosis steps, logging to add, verification checklist, and comms template. Keep under 160 words. Incident: {{details}}

Design feature flags for {{feature}}: rollout steps, default states, kill-switch rules, and telemetry to track. Keep under 150 words.

Summarize risky dependencies: outdated, security advisories, heavy size, or single maintainer. Recommend upgrade order and mitigations. Keep under 170 words. List: {{paste}}

Improve this CLI UX: command description, flags, examples, and error handling. Return a revised help text and one sample workflow. Keep under 170 words. Current help: {{paste}}

Rewrite confusing code comments to explain intent, invariants, and gotchas. Keep each under 25 words. Comments: {{paste}}

List edge cases and failure modes for {{feature}} across inputs, state, concurrency, and integration. Provide a checklist under 140 words.

Explain this regex in plain language, including what it matches, examples, and pitfalls. Keep under 140 words. Regex: {{pattern}}

Create a 45-minute pairing agenda for {{task}} with setup, driving/navigating swaps, checkpoints, and a retro question. Keep under 110 words.

Turn these changes into great commit messages using the format: title in imperative, body with what/why, and risks. Provide 2 options. Changes: {{paste}}

Plan a safe monorepo change: packages touched, test suites to run, release steps, and owners to notify. Keep under 170 words. Change: {{details}}

Describe how to set up a realistic sandbox for {{system}} with sample data, auth, and environment variables. Keep under 160 words.

Write a concise SDK usage example for {{feature}} with setup, minimal code, and error handling. Keep code under 25 lines.

Plan how to mock external APIs for {{feature}}: endpoints, sample payloads, failure cases, and verification. Keep under 150 words.

Create a discovery call plan for {{prospect}}. Include opener, 6 problem questions, 3 impact questions, budget/timeline checks, and close with next step. Keep under 160 words.

Write a concise follow-up email after a call: thank you, 3-value bullets tailored to their goals, next step ask with 2 time options. Keep under 110 words. Context: {{notes}}

Provide 4 responses for the objection '{{objection}}'. Each response: empathy, short proof, one question. Keep each under 30 words.

Create a quick ROI snapshot for {{product}}. Inputs: price, baseline metric, expected lift. Output: payback time, 1 proof point, and a one-liner pitch. Keep under 130 words.

Draft a mutual action plan: milestones, owners (us/them), due dates, and risks. Add a one-line success definition. Keep under 150 words. Deal: {{details}}

Write a 10-minute demo script for {{product}}. Sections: set agenda, 3 pains, 3 feature moments tied to pains, proof point, next step. Keep under 170 words.

Build a qualification checklist using MEDDIC-style prompts: metrics, economic buyer, decision process, decision criteria, pain, champion. Return as questions to ask. Keep under 140 words.

Analyze deal notes and list risks: missing champion, timeline slippage, unseen competitor, legal delay, weak ROI. Provide a mitigation for each. Keep under 150 words. Notes: {{paste}}

Create a battlecard for competitor {{name}}: summary, 3 strengths, 3 counters, proof, trap questions, and landmines to avoid. Keep under 180 words.

Provide a pricing call guide: anchoring statement, 3 discovery questions, ROI framing, objection handling, and a close. Keep under 140 words.

Draft an expansion play for an existing customer: health signals, new stakeholders to engage, relevant upsell features, and 2 call scripts. Keep under 180 words. Customer: {{details}}

Create a renewal save plan: risk signals, 3 questions to surface value gaps, offer options, and a success metric. Keep under 150 words. Account: {{details}}

Write a one-pager for a champion to circulate internally: problem framing, desired outcomes, proof, timeline, and ask. Keep under 160 words. Context: {{details}}

Draft a warm intro request message: relevance, ideal contact description, how to forward, and gratitude. Keep under 80 words.

Provide 5 cold call openers for {{persona}} that are respectful, concise, and curiosity-based. Keep each under 18 words.

Create a call recap template with sections: goals heard, pains, agreed value, next steps, timeline, risks. Keep under 120 words.

Outline a sales proposal: summary, objectives, scope, assumptions, pricing options, timeline, success metrics, terms. Keep under 170 words.

List a procurement checklist: security review, legal, data handling, billing, approvals, and decision maker. Provide suggested owner/time for each. Keep under 150 words.

Define pilot success criteria for {{product}}: measurable goal, timeline, data to collect, decision date, and exit options. Keep under 140 words.

Create a 90-day territory plan: ICP segments, target accounts, activity targets, top plays, and review cadence. Keep under 180 words.

Provide an account research template: company overview, recent news, tech stack hints, hiring signals, and 3 tailored hypotheses to test. Keep under 170 words. Account: {{name}}

Build a first-call agenda: rapport, 3 discovery topics, pain confirmation, quick value story, next step. Keep under 120 words.

Write 4 voicemail scripts for {{persona}}. Each: relevance hook, value promise, and callback ask. Keep each under 25 words.

Design a 5-step outbound email sequence with subject, angle, CTA, and wait time. Steps: intro, pain, proof, objection, close. Keep under 190 words.

Write a briefing for a CFO: concise business case, cost, ROI estimate, risk mitigations, and implementation plan. Keep under 160 words. Context: {{details}}

List upsell triggers for {{product}} with detection cues (usage, roles, events) and tailored offers. Keep under 150 words.

Draft a proof-of-concept plan: scope, success criteria, data/setup needs, milestones, and sign-off plan. Keep under 170 words.

Write a short social DM to {{persona}} that references a recent post, shares a relevant insight, and asks a light question. Keep under 70 words.

Provide language to handle discount requests: value reframe, trade-off ask (term, case study), and a floor reminder. Keep under 90 words.

Draft a close plan for {{deal}}: decision process, key dates, stakeholders, legal steps, and success criteria. Keep under 170 words.

Create a triage playbook: severity definitions, first response goals, info to collect, and routing rules. Keep under 160 words.

Write a first reply that is empathetic and concise. Include apology if needed, summary of issue, ask for one detail, and promise next update time. Keep under 90 words. Issue: {{details}}

Draft a template asking for reproduction info: steps, expected vs actual, screenshots/logs, account ID, browser/app version, and timezone. Keep under 80 words.

Write an escalation note: summary, impact, attempts made, logs/links, urgency, and clear ask. Keep under 110 words. Case: {{details}}

Draft a status page post: incident summary, impact, start time, current mitigation, next update time, and workaround. Keep under 120 words. Incident: {{details}}

Send a polite SLA reminder: current status, apology, expected resolution time, and escalation option. Keep under 70 words. Case: {{details}}

Outline a help article: summary, symptoms, step-by-step fix, screenshots needed, FAQs, and when to contact support. Keep under 170 words. Topic: {{topic}}

Write an outage email: brief what happened, impact, reassurance, workaround, next update time, and apology. Keep under 130 words. Incident: {{details}}

Draft a refund response: acknowledge issue, eligibility statement, next steps, timing expectations, and a retention offer if appropriate. Keep under 100 words. Case: {{details}}

Rewrite this support reply to be calm, concise, and confident. Keep under 90 words and add one empathic sentence. Reply: {{paste}}

Create a template to capture feature requests: customer goal, current workaround, frequency, value, and urgency. Keep under 90 words. Request: {{details}}

Given a new ticket, suggest potential duplicates and a merge note. Include what to keep and what to close. Keep under 120 words. Tickets: {{paste}}

Identify churn risk signals in this conversation and propose 3 save actions with owners. Keep under 140 words. Transcript: {{paste}}

Create 5 macros for common issues in {{product}}. Each: greeting, fix steps, link placeholder, close. Keep each under 60 words.

Write a bilingual reply (English + {{language}}) summarizing the issue, the fix, and next steps. Keep each language under 80 words. Issue: {{details}}

Provide an API support checklist: endpoint, request ID, payload, response, timestamps, and auth method. Add 3 quick diagnostics. Keep under 110 words.

Draft a template asking customers for logs or screenshots securely. Include why, how to share, and masking guidance. Keep under 90 words.

Write an internal handoff: customer context, current status, promised actions, urgency, and next update time. Keep under 120 words. Ticket: {{details}}

Summarize root cause after a fix: issue, trigger, impact, fix applied, prevention steps. Keep under 110 words. Incident: {{details}}

Explain SLO/SLA terms to a customer in plain language and set expectations for this ticket. Keep under 80 words.

Turn a support fix into a micro-education moment: recap issue, why it happens, preventive tip, and link to docs. Keep under 100 words. Issue: {{details}}

Summarize new release items that support should know: new behaviors, known issues, workaround, and key talking points. Keep under 170 words. Release: {{details}}

Estimate support queue for today using past volumes. Provide expected tickets per hour and staffing suggestion. Keep under 130 words. Data: {{paste}}

Write an apology for a delayed response: acknowledge delay, brief reason, current status, and next update time. Keep under 80 words. Ticket: {{details}}

Summarize a bug for engineering: impact, repro steps, scope (users/regions), severity, logs, and attachments. Keep under 140 words. Ticket: {{details}}

Draft a proactive message to customers likely impacted by {{issue}}: symptom, quick check, workaround, and how to confirm fix. Keep under 110 words.

Provide coaching on this agent reply: what worked, what to improve, and a revised version. Keep under 150 words. Reply: {{paste}}

Design a CSAT recovery message after a low score: acknowledgment, fix summary, offer to help live, and feedback ask. Keep under 90 words.

Create a grooming checklist for support backlog: duplicates, stale tickets, blocked tickets, and prioritization cues. Keep under 120 words.

Draft a 5-question survey to measure support satisfaction: speed, clarity, empathy, resolution, and overall. Keep under 90 words.

Create a research plan for {{goal}}. Include objectives, methods, participants, artifacts, timeline, and success signals. Keep under 180 words.

Draft a screener survey with 6 questions to recruit users for {{study}}. Include disqualifiers, role, frequency, and tool usage. Keep under 120 words.

Write a usability test script: intro, consent, 4 tasks, 2 follow-up questions per task, and closing. Keep under 170 words. Prototype: {{details}}

List 3 persona hypotheses for {{product}} with job-to-be-done, pain, trigger event, and success measure. Keep under 150 words.

Create a journey map skeleton: stages, user goals, actions, emotions, pain points, and opportunities. Keep under 170 words. Scenario: {{details}}

Build a competitor matrix: positioning, key features, pricing notes, unique angle, and gaps. Provide 3 insights. Keep under 170 words. Competitors: {{list}}

Estimate TAM/SAM/SOM for {{market}} using top-down and bottom-up notes. Provide assumptions and quick math. Keep under 170 words.

Summarize secondary research on {{topic}}: 5 key findings, sources, contradictions, and gaps to validate. Keep under 170 words. Sources: {{paste}}

Cluster these qualitative responses into themes. Return theme name, supporting quotes, and implication. Keep under 200 words. Responses: {{paste}}

Create a Jobs-to-be-Done interview guide: push, pull, anxiety, habit, and success definitions. 6–8 questions. Keep under 160 words. Context: {{details}}

Design a 2-week diary study: tasks, daily prompts, capture format (text/photo), incentives, and check-ins. Keep under 180 words. Topic: {{topic}}

Turn these insights into testable hypotheses with metric, audience, and expected direction. Keep under 170 words. Insights: {{paste}}

Prioritize insights using impact, confidence, and ease. Return ranked list with one action each. Keep under 150 words. Insights: {{paste}}

Outline a research readout: objectives, methods, key findings, quotes, implications, and decisions needed. Keep under 170 words. Study: {{details}}

QA this survey for bias, clarity, and order effects. Suggest fixes and a soft-launch plan. Keep under 160 words. Survey: {{paste}}

Given mixed feedback, separate signal from noise. Tag each item as signal/noise with rationale and next step. Keep under 170 words. Feedback: {{paste}}

Draft a win/loss interview guide: decision drivers, competitor perception, evaluation path, and future intent. Keep under 150 words. Deal: {{details}}

Turn raw feedback into user stories with acceptance criteria. Keep under 170 words. Feedback: {{paste}}

Create an ethics checklist for {{study}}: consent, incentives, data handling, anonymity, and opt-out path. Keep under 140 words.

Map assumptions for {{project}} into high/low certainty vs impact. Suggest 3 validation actions. Keep under 150 words.

Clean messy field notes into bullets: observation, quote, inference, and time stamp. Keep under 170 words. Notes: {{paste}}

Write a participant briefing: purpose, what to expect, duration, privacy, and how to prepare. Keep under 130 words. Study: {{details}}

Plan data collection for {{study}}: sources, fields, frequency, storage, and quality checks. Keep under 170 words.

Create a log template for competitor teardowns: page link, hook, offer, CTA, pricing cues, and takeaway. Keep under 150 words.

Turn top findings into a story: setup, tension, turning point, and recommendation. Keep under 160 words. Findings: {{paste}}

Organize quotes into themes with attribution and suggested use (web, sales, ads). Keep under 170 words. Quotes: {{paste}}

Build a problem tree: root causes, branches of contributing factors, and quick tests to validate each. Keep under 170 words. Problem: {{details}}

Propose a taxonomy for a research repo: tags for persona, journey stage, product area, method, and confidence. Keep under 150 words.

Translate an insight into an experiment idea: hypothesis, metric, variant, and rollout rule. Keep under 140 words. Insight: {{paste}}

Summarize competitor timeline: key launches, pricing changes, funding, and shifts in messaging. Provide 3 implications. Keep under 180 words. Competitor: {{name}}

Design a 2-week learning sprint for {{topic}}. Include daily goal, 30-minute exercise, and reflection question. Keep under 170 words.

Generate 10 spaced-repetition Q&A cards for {{concept}}. Keep answers under 20 words and ensure one fact per card.

Explain {{topic}} in 3 levels: child, student, practitioner. Each level under 80 words with examples.

Create 5 practice drills for {{skill}} with timeboxing, expected output, and self-check questions. Keep under 150 words.

List common mistakes for {{skill}} and how to avoid them. Provide quick fixes. Keep under 150 words.

Create a one-page cheat sheet for {{topic}}: key formulas/steps, pitfalls, and quick examples. Keep under 200 words.

Define 5 SMART learning goals for {{skill}} with milestones and evidence of completion. Keep under 150 words.

Create a plan to teach {{topic}} to a peer: outline, demo idea, interactive exercise, and quiz question. Keep under 170 words.

Generate 5 analogies to explain {{concept}} using everyday objects. Keep each under 20 words and avoid repetition.

Build a reading plan for {{topic}}: order sources, what to extract, and reflection prompts. Keep under 150 words. Sources: {{paste}}

Create a 10-question quiz on {{topic}} with multiple choice answers and a key. Mix easy and tricky items. Keep under 220 words.

Check my explanation of {{concept}} for clarity. Point out gaps and rewrite it plainly under 120 words. Explanation: {{paste}}

Outline steps to move from beginner to intermediate in {{skill}}: foundations, projects, feedback loops, and benchmarks. Keep under 170 words.

Design a deliberate practice plan: one sub-skill focus, measurable rep count, feedback method, and reflection questions. Keep under 150 words. Skill: {{skill}}

Create a 60-minute study group agenda for {{topic}}: warm-up, group exercise, peer review, and commitments. Keep under 120 words.

Give 5 tactics to retain {{topic}} better, citing time intervals or cues. Keep under 120 words.

Suggest 3 portfolio-worthy projects to learn {{skill}}. Include problem statement, constraints, and success signals. Keep under 150 words.

Write a template to request feedback on {{work}} with context, goals, and 3 focused questions. Keep under 90 words.

Prepare for office hours: summarize what I tried, where I'm stuck, hypotheses, and specific questions. Keep under 120 words. Topic: {{topic}}

Design a 5-day microlearning sequence (10 minutes/day) for {{topic}}: concept, example, quick exercise, and self-check. Keep under 170 words.

Outline a knowledge transfer doc: overview, why it matters, key steps, common traps, and resources. Keep under 150 words. Topic: {{topic}}

Identify skill gaps for {{role}} based on current vs desired proficiency. Suggest 3 actions per gap. Keep under 170 words.

Provide 7 reflection prompts to deepen learning after working on {{topic}}. Keep each under 15 words.

Turn theory into practice: propose 3 real-life tasks to apply {{concept}}, with success signals. Keep under 140 words.

Create a mentor brief: goals, current level, recent work, feedback preferences, and session ask. Keep under 120 words.

Build a 3-day cram plan for {{exam}}: priority topics, practice schedule, rest, and mock test timing. Keep under 170 words.

Create a teach-back checklist: main idea, 3 supporting points, example, counterexample, and one-question quiz. Keep under 120 words. Topic: {{topic}}

Design a maintenance routine to keep {{skill}} sharp: weekly reps, monthly review, and a small challenge. Keep under 150 words.

Draft a community post asking for help on {{topic}}. Include what I tried, 2 questions, and gratitude. Keep under 90 words.

Create a self-check to calibrate confidence on {{topic}}: 5 statements to rate, then tailored next steps. Keep under 150 words.

Provide a design critique using: goal clarity, hierarchy, spacing, alignment, contrast, and accessibility. Give 5 actionable improvements. Keep under 170 words. Design summary: {{paste}}

Run an accessibility check: color contrast tips, focus order, alt text guidance, and keyboard traps to test. Keep under 140 words. Screen: {{details}}

Outline a wireframe for {{page}}: sections, goals per section, primary/secondary actions, and data needed. Keep under 170 words.

Draft initial design tokens: colors, typography scale, spacing scale, radius, shadows. Provide naming suggestions. Keep under 170 words.

Create 4 empty state concepts for {{feature}}. Include message, illustration idea, and first action. Keep each under 30 words.

Design a 4-step onboarding flow: welcome, key benefit, setup action, success screen. Include copy prompts and success metric. Keep under 170 words.

Give CTA design tips for {{page}}: color/placement, microcopy, surrounding proof, and hover/focus states. Keep under 140 words.

Suggest hierarchy fixes: where to add emphasis, reduce noise, align grids, and adjust spacing. Keep under 150 words. Screen summary: {{paste}}

Propose card layout patterns for {{content}}: image/text balance, metadata placement, actions, and responsive behavior. Keep under 170 words.

Review a form: label clarity, grouping, error handling, defaults, and mobile ergonomics. Provide 5 fixes. Keep under 170 words. Form details: {{paste}}

Create a brief for an icon set: theme, line weight, corner radius, grid size, and examples of 5 icons. Keep under 160 words.

Write motion guidelines: easing types, durations for entrances/exits, stagger rules, and when to avoid motion. Keep under 170 words.

Provide a design QA checklist: spacing, typography, colors, states, responsiveness, and accessibility. Keep under 170 words.

Outline a dashboard layout for {{metrics}}: hero metric, trends, comparisons, and alerts. Include interaction ideas. Keep under 170 words.

Translate brand words into visuals: color cues, typography choices, shape language, and imagery style. Keep under 170 words. Brand words: {{list}}

Check this design for mobile-first: thumb reach, tap targets, stacking order, and font sizes. Provide 5 fixes. Keep under 150 words. Screen: {{details}}

Suggest table UX improvements: sorting/filtering defaults, density options, empty/overflow states, and inline actions. Keep under 170 words.

Build a color palette: primary, neutrals, semantic (success/warn/error), and accent. Provide contrast considerations. Keep under 170 words.

Propose 3 hero section layouts with headline placement, supporting visual idea, CTA, and trust element. Keep under 140 words. Goal: {{goal}}

Design notification patterns: priority levels, channels, timing rules, and preference center outline. Keep under 170 words.

Suggest progress indicator patterns for {{flow}}: stepper, inline, skeleton, and optimistic UI notes. Keep under 160 words.

Recommend search UX improvements: placeholder guidance, filters, result clarity, empty states, and keyboard shortcuts. Keep under 170 words.

Propose an IA for {{product}}: top nav, secondary nav, key destinations, and naming. Keep under 170 words.

Provide layout rules for long-form content: column width, line height, typography pairing, and callout styles. Keep under 170 words.

Suggest steps to improve design system adoption: contribution model, changelog, training, and component readiness criteria. Keep under 170 words.

Design error states: clear title, plain-language cause, recovery action, and help link. Provide 3 examples. Keep under 160 words.

Make a pre-ship design checklist: alignment, copy review, state coverage, load/empty/error, and responsive checks. Keep under 150 words.

Write a card sorting session script: intro, instructions, prompts, and debrief questions. Keep under 170 words. Content: {{details}}

Suggest microinteractions for {{feature}}: triggers, feedback, timing, and accessibility considerations. Keep under 170 words.

Create a design handoff checklist: specs, assets, states, acceptance criteria, and open questions. Keep under 150 words.

Generate 12 ideas for {{goal}} across 4 lenses: product, marketing, partnerships, and operations. Keep each under 18 words.

Brainstorm 8 ideas for {{goal}} assuming a hard constraint (zero budget, 1-week timeline, or solo execution). Keep each under 15 words.

List ways to make {{problem}} worse, then flip each into a prevention idea. Provide 6 pairs. Keep each idea under 15 words.

Use analogies from 5 industries to spark ideas for {{topic}}. Provide 2 ideas per industry. Keep each under 16 words.

Generate 10 ideas for {{goal}} by focusing on customer jobs, pains, and desired outcomes. Keep each under 16 words.

Suggest 8 zero-to-one ideas for {{space}} that challenge assumptions. Provide a one-line rationale each. Keep under 130 words total.

List 10 ideas to repurpose existing assets (content, data, partnerships) for {{goal}}. Keep each under 15 words.

Propose 10 small bets (cheap, fast tests) to validate {{hypothesis}}. Include expected signal for each. Keep under 170 words.

Brainstorm 8 ways to remove steps from {{process}} without losing quality. Keep each idea under 14 words.

Suggest 10 delight moments for {{experience}} that are low effort, high joy. Keep each under 15 words.

Borrow from 5 industries to solve {{problem}}. Provide 2 ideas per industry with one-line rationale. Keep under 180 words.

Imagine success in 3 years for {{goal}}. List 8 milestones that must be true. Keep under 140 words.

Brainstorm 6 alternatives if a core feature vanished. For each, note benefit and risk. Keep under 160 words. Feature: {{feature}}

Write 6 elevator pitches for {{idea}} using different angles: ROI, speed, simplicity, safety, fun, and mission. Keep each under 25 words.

Generate 12 name ideas for {{product}}. Mix descriptive, metaphorical, and playful styles. Keep each under 3 words.

List 10 partnership ideas for {{audience}} including co-marketing, bundles, referrals, and data shares. Keep each under 16 words.

Suggest 8 event ideas (virtual or IRL) for {{goal}}. Include target audience and core promise. Keep each under 18 words.

Generate 10 retention ideas for {{product}} across onboarding, habit loops, and win-backs. Keep each under 16 words.

List 10 acquisition experiments with channel, concept, and expected signal. Keep under 170 words. Goal: {{goal}}

Propose 8 monetization ideas for {{product}}: pricing levers, add-ons, bundles, or usage tiers. Keep each under 18 words.

Suggest 10 process improvements for {{team}}. Include impact guess and first step. Keep under 170 words.

Generate 8 community-building ideas for {{audience}}: prompts, events, challenges, or recognition. Keep each under 18 words.

List 8 trust-building moves for {{prospect}}: proof points, guarantees, transparent pricing, or live examples. Keep each under 16 words.

Give 10 time-saving ideas for {{workflow}}: automation, templates, shortcuts, or batching. Keep each under 15 words.

Brainstorm 8 ways to add delight to support interactions. Keep each idea under 16 words.

Suggest 10 metrics for {{goal}} with a one-line why. Avoid vanity metrics. Keep under 170 words.

Generate 12 content ideas for {{audience}}. Mix how-to, teardown, myth-busting, and checklists. Keep each under 14 words.

List 8 hooks that make {{product}} habit-forming: triggers, rewards, social proof, streaks. Keep each under 16 words.

Propose 10 story angles for {{topic}}: origin, antagonist, before/after, data-led, customer hero. Keep each under 16 words.

List 8 ways to reduce risk for {{initiative}}: pilots, staging, contracts, monitoring, or training. Keep each under 16 words.

Draft OKRs for {{team}}. Provide 1–3 objectives and 3 key results each with measurable targets. Keep under 170 words.

Recommend a North Star metric and 3 guardrail metrics for {{product}} with rationale. Keep under 150 words.

Create a SWOT snapshot for {{company}} with 3 bullets per quadrant and a one-line implication. Keep under 170 words.

Suggest 5 roadmap themes for {{goal}} with sample initiatives and success signals. Keep under 170 words.

Rank initiatives using impact, confidence, effort. Return a table sorted by score with a one-line action. Keep under 170 words. Items: {{paste}}

Analyze potential moats for {{product}}: network effects, data, brand, distribution, switching costs. Provide risks. Keep under 170 words.

Create best/base/worst-case scenarios for {{plan}} with key assumptions and triggers to switch paths. Keep under 170 words.

Build a risk register: risk, likelihood, impact, owner, mitigation, and trigger to act. Keep under 180 words. Context: {{details}}

Summarize competitive positioning: target, value prop, differentiation, and proof. Provide 3 moves to strengthen position. Keep under 170 words. Competitors: {{list}}

Draft an investment thesis for {{initiative}}: problem, opportunity size, why now, edge, and key risks. Keep under 180 words.

Outline a market entry plan: ICP, wedge use case, channels, pricing hint, and success metric. Keep under 170 words. Market: {{details}}

Write a decision memo: context, options, criteria, recommendation, risks, and next steps. Keep under 170 words. Decision: {{details}}

Propose resource allocation for {{team}} across priorities with percentages and rationale. Keep under 150 words.

Craft a strategic narrative: status quo, shift, promised land, obstacles, and how we help. Keep under 170 words. Audience: {{audience}}

Outline a pricing strategy: target segments, value metric, tiering logic, and monetization risks. Keep under 170 words. Product: {{details}}

Build a KPI tree for {{goal}}: North Star, drivers, input metrics. Include owner hints. Keep under 170 words.

Design an operating cadence: weekly, monthly, quarterly rituals with purpose, inputs, and outputs. Keep under 170 words.

Plan a change rollout: stakeholders, risks, comms sequence, training, and feedback loops. Keep under 170 words. Change: {{details}}

Define a partner strategy: target partner types, value exchange, first offers, and success metrics. Keep under 170 words.

Size product bets: effort t-shirt size, upside, downside, confidence, and learning value. Return a ranked list. Keep under 180 words. Bets: {{paste}}

Create a Stop/Start/Continue list for {{team}} with rationale and expected impact. Keep under 150 words.

Outline a board update: highlights, lowlights, metrics, asks, and decisions needed. Keep under 170 words.

Propose defensive moves against competitor {{name}}: retention plays, pricing responses, and differentiation angles. Keep under 170 words.

Build an experiment portfolio: quick wins, core improvements, and big bets with expected learning. Keep under 170 words.

Draft a concise mission, vision, and 4 values for {{team/company}} with behavior examples. Keep under 180 words.

Create a go/no-go checklist for a launch: readiness criteria across product, marketing, ops, support. Keep under 170 words. Launch: {{details}}

Translate roadmap items into a narrative for customers: promise, upcoming themes, and what to expect next. Keep under 180 words. Roadmap: {{paste}}

Describe trade-offs for reallocating {{resource}}: what slows, what speeds up, and mitigation ideas. Keep under 150 words.

Define exit criteria for killing or doubling down on {{initiative}}: metric thresholds, time limits, and learning goals. Keep under 170 words.

Connect metrics to decisions: for each key metric, list what we will do if it rises/falls. Keep under 170 words. Metrics: {{paste}}

Create keyword clusters for {{topic}}: primary term, 5 supporting terms, and intent. Keep under 150 words.

Analyze the SERP for '{{keyword}}': search intent, top formats, common headings, and gaps. Keep under 170 words.

Write a content brief: target keyword, angle, outline with H2/H3, FAQs, and internal links. Keep under 200 words. Keyword: {{keyword}}

Generate 5 SEO titles (<=60 chars) and meta descriptions (<=155 chars) for {{page}}. Include primary keyword naturally.

Recommend schema types and key properties for {{page}} (FAQ, Article, Product, HowTo, etc.). Keep under 170 words.

Plan internal links for {{page}}: 5 anchor ideas from existing pages and 3 onward links. Keep under 150 words.

Outline a content refresh: update stats, add section, improve intro/CTA, fix links, and add FAQ. Keep under 170 words. Page summary: {{paste}}

Provide a lite technical audit checklist: crawlability, indexation, sitemaps, robots, Core Web Vitals, redirects, and canonicals. Keep under 180 words.

Suggest 10 backlink ideas for {{topic}}: guest posts, data studies, tools, partnerships. Keep each under 18 words.

Write 6 FAQ Q&As targeting {{keyword}}. Answers under 40 words, concise and snippet-friendly.

Give image SEO guidance: filenames, alt text, compression, dimensions, lazy loading, and context. Keep under 140 words.

Provide a local SEO checklist: GMB, NAP consistency, local pages, reviews, and citations. Keep under 150 words.

Brainstorm 8 linkable asset ideas for {{industry}}: data reports, calculators, templates, or tools. Keep each under 18 words.

Suggest fixes for thin content on {{site}}: consolidation, expansion ideas, and deletion criteria. Keep under 170 words.

Propose a URL structure for {{site}}: hierarchy, naming rules, and redirect guidelines. Keep under 150 words.

Provide a plan to improve LCP, FID, CLS for {{page}} with concrete fixes. Keep under 170 words.

Identify keyword/content gaps vs competitors {{list}}. Suggest 5 pages to build with target terms. Keep under 180 words.

Create an anchor text distribution plan: exact, partial, branded, generic percentages for {{keyword}} page. Keep under 140 words.

Recommend ways to improve E-E-A-T on {{page}}: author creds, sources, first-party data, and trust signals. Keep under 160 words.

Write an SOP for internal linking: how to choose anchors, frequency, link depth, and QA. Keep under 170 words.

Plan redirects for {{migration}}: mapping, canonical strategy, and monitoring. Keep under 160 words.

List 8 seasonal SEO ideas for {{industry}} with timing and angle. Keep each under 18 words.

Provide international SEO guidance: hreflang setup, content localization, URL structure, and regional keyword research. Keep under 180 words.

Design a content pruning plan: metrics to evaluate, keep/merge/remove rules, and tracking. Keep under 170 words.

Optimize for featured snippets on {{keyword}}: answer format, schema, and heading tweaks. Keep under 150 words.

Review sitemap strategy: what to include/exclude, update frequency, and monitoring. Keep under 150 words. Site: {{details}}

Propose a blog taxonomy: categories, tags, and rules to avoid cannibalization. Keep under 170 words.

Provide a page speed checklist: image optimization, caching, critical CSS, script loading, and monitoring. Keep under 170 words.

Outline analytics tracking for SEO: goals, events, search console checks, and dashboards. Keep under 170 words.

Turn this keyword and intent into an outline with headings, key points, and CTA. Keep under 170 words. Keyword: {{keyword}}

Generate 12 hooks for {{topic}} tailored to {{platform}}. Mix curiosity, number, contrarian, question, and how-to formats. Keep each under 12 words.

Outline a 7-tweet thread on {{topic}}: hook, 5 value tweets, CTA. Add emoji guidance if relevant. Keep under 170 words.

Write a 45-second video script for {{platform}} on {{topic}}: hook, 3 tips, CTA. Include shot suggestions. Keep under 170 words.

Plan a 6-slide carousel: cover hook, problem, 3 tips, recap, CTA. Add headline for each slide. Keep under 170 words. Topic: {{topic}}

Provide 8 engaging comments to add under industry posts about {{topic}} that add value and invite replies. Keep each under 22 words.

Recommend a 4-week posting cadence for {{platform}}: frequency, content types, themes, and CTA variety. Keep under 180 words.

Turn this long-form piece into posts for LinkedIn, Twitter, TikTok, and email. Summarize angles, hooks, and CTAs. Keep under 200 words. Content: {{paste}}

Write 10 community prompts/questions for {{audience}} that spark replies and stories. Keep each under 18 words.

Draft a respectful DM to {{persona}} referencing their recent post and offering a helpful resource. Keep under 70 words.

Outline a 5-frame story series: hook, context, value tip, proof, swipe-up CTA placeholder. Keep under 150 words. Topic: {{topic}}

Suggest 3 hashtag sets (broad, niche, branded) for {{topic}} and {{platform}}. Keep total under 120 words.

Write a social post addressing {{issue}}: brief facts, empathy, link to details, and commitment. Keep under 120 words.

Translate analytics into content moves: what to post more/less, best timing, and CTA tweaks. Keep under 170 words. Metrics: {{paste}}

Create 5 social proof post ideas using testimonials, numbers, before/after, and screenshots. Keep each under 18 words.

Write 3 event promo posts with hook, who it's for, what they'll get, and link placeholder. Keep each under 45 words. Event: {{details}}

Draft an AMA announcement: topic, date/time, what people can ask, and how to join. Keep under 90 words.

Rewrite this post to match brand voice (choose: bold, friendly, witty, expert). Keep under 80 words. Post: {{paste}}

Provide 7 engagement boosters for {{platform}}: polls, questions, challenges, duets, or stitch ideas. Keep each under 18 words.

Plan a 5-post countdown series for {{launch}}: themes, hooks, and CTA for each day. Keep under 170 words.

Suggest 6 ways to prompt UGC for {{product}} and how to request permission. Keep under 130 words.

Show how to remix one post across Twitter, LinkedIn, Instagram, and TikTok with tweaks per platform. Keep under 180 words. Post: {{paste}}

Give 8 hook and visual pairings for {{topic}} (photo, chart, clip, text card). Keep each under 18 words.

Optimize a profile bio: value promise, proof point, CTA, and link strategy for {{platform}}. Keep under 120 words. Current bio: {{paste}}

Provide moderation replies for common comment types: praise, complaint, spam, off-topic, and suggestion. Keep each under 25 words.

Draft a brief for creators: goal, key message, do/don't, required tags, and timeline. Keep under 170 words. Campaign: {{details}}

Summarize social performance: top posts, growth, engagement rate, retention, and next experiments. Keep under 170 words. Data: {{paste}}

Create 6 fill-in-the-blank caption templates for {{platform}} to save time. Keep each under 20 words.

Suggest 10 keywords/phrases to monitor for {{audience}} and how to respond or engage. Keep under 170 words.

Write a crisis response playbook: approval chain, holding statement, monitoring, and recovery content. Keep under 180 words.

Provide 14 daily prompts for {{audience}} mixing tips, questions, stories, and CTAs. Keep each under 18 words.

Create a PRD outline for {{feature}}: problem, goals, non-goals, users, flows, requirements, risks, metrics. Keep under 200 words.

Write 5 user stories for {{feature}} with acceptance criteria in Given/When/Then. Keep each under 60 words.

Draft release notes: what changed, who it's for, impact, how to enable, and known issues. Keep under 160 words. Feature: {{details}}

Create an adoption plan: launch audience, messaging, enablement assets, in-product cues, and success metrics. Keep under 180 words. Feature: {{details}}

Provide a backlog grooming checklist: clarify stories, split, estimate, de-duplicate, and rank. Keep under 150 words.

Write a roadmap narrative: themes, customer promises, sequencing rationale, and risks. Keep under 180 words. Inputs: {{details}}

Draft an instrumentation plan: events, properties, funnels, and success metrics for {{feature}}. Keep under 180 words.

Design an experiment for {{hypothesis}}: metric, variant, sample size hint, guardrails, and stop rule. Keep under 180 words.

Create an interview pack: goal, 8 questions, demo tasks, and success signals to observe. Keep under 180 words. Topic: {{topic}}

Map product metrics to actions: for each metric, list a decision if it rises/falls. Keep under 170 words. Metrics: {{paste}}

Write a crisp problem statement: who, pain, impact, evidence, and why now. Keep under 120 words. Context: {{details}}

List top alternatives to {{product}} and why customers pick them. Provide 3 counter-messaging ideas. Keep under 170 words.

Define success metrics for {{feature}}: activation, engagement, retention, and quality. Add event names. Keep under 170 words.

Provide a launch checklist: tech readiness, QA, analytics, docs, support, comms, and rollback. Keep under 180 words. Feature: {{details}}

Create a feature kill evaluation: usage, support cost, revenue impact, and migration plan. Keep under 170 words. Features: {{paste}}

Plan a beta: recruit criteria, success measures, feedback loops, and exit criteria. Keep under 180 words. Feature: {{details}}

Write in-app copy for {{moment}}: title, body, primary/secondary CTAs, and success message. Keep under 120 words.

List guardrail metrics for {{experiment}} to protect UX, revenue, and reliability. Keep under 150 words.

Identify journey drop-offs and propose 5 fixes with expected impact. Keep under 170 words. Journey notes: {{paste}}

Summarize customer feedback by theme with volume, severity, and a recommended action. Keep under 170 words. Feedback: {{paste}}

Assess release risk: blast radius, dependencies, rollback ease, and monitoring plan. Keep under 170 words. Release: {{details}}

Write a feature brief: goal, user story, acceptance criteria, UX notes, and analytics. Keep under 170 words. Feature: {{details}}

Draft a stakeholder update: status, risks, decisions needed, next milestones, and demo link. Keep under 150 words. Project: {{details}}

Provide scoping guardrails: MVP definition, nice-to-haves, constraints, and success criteria. Keep under 170 words. Feature: {{details}}

Suggest 10 actions to improve NPS for {{product}} across onboarding, UX, support, and reliability. Keep each under 18 words.

Create a request intake form: problem, users affected, impact, deadline, and links. Keep under 120 words. Request type: {{type}}

Generate 8 feature names with style notes (descriptive, metaphorical, playful) for {{feature}}. Keep each under 4 words.

Review adoption metrics and suggest 3 moves: UX, messaging, or incentives. Keep under 150 words. Metrics: {{paste}}

Run a release debrief: what worked, surprises, incidents, user feedback, and improvements. Keep under 160 words. Release: {{details}}

Write a product strategy one-pager: mission, target user, promise, moat, 3-year bets, and risks. Keep under 200 words.

Design an event taxonomy for {{product}}: key events, properties, naming rules, and ownership. Keep under 180 words.

Write a dashboard brief: audience, decisions it supports, core charts, refresh cadence, and data sources. Keep under 170 words. Goal: {{goal}}

Plan a funnel analysis: steps, success metric, drop-off questions, and segment ideas. Keep under 170 words. Funnel: {{details}}

Design a cohort retention study: cohort definition, time buckets, metrics, and hypotheses. Keep under 170 words. Product: {{details}}

Create an anomaly investigation playbook: validate data, segment, check releases, and communicate impact. Keep under 170 words. Metric: {{metric}}

Write clear definitions for these metrics with SQL-ish logic, edge cases, and owner. Keep under 180 words. Metrics: {{paste}}

Check experiment readiness: hypothesis, primary/guardrail metrics, sample size note, randomization, and tracking. Keep under 170 words. Experiment: {{details}}

Draft a clear analytics request: question, decision, time range, dimensions, filters, and output format. Keep under 130 words.

Summarize attribution options for {{funnel}}: models to compare, data needed, and pitfalls. Keep under 170 words.

Create a churn analysis plan: cohort definition, signals to test, segments, and outputs. Keep under 170 words.

Review current North Star and drivers, flag vanity metrics, and suggest 3 better drivers. Keep under 170 words. Context: {{details}}

Provide a data quality checklist: freshness, completeness, uniqueness, validity, and lineage. Keep under 170 words.

Suggest 10 useful segments for {{goal}} with a one-line why. Keep under 170 words.

Build a goal tree: top goal, sub-goals, and metrics to monitor. Keep under 170 words. Goal: {{goal}}

Turn these metrics into a story: context, change, cause hypotheses, and action. Keep under 170 words. Metrics: {{paste}}

Outline a forecast for {{metric}}: assumptions, model type, scenarios, and validation plan. Keep under 170 words.

Create an instrumentation QA checklist: event fires, properties, edge cases, and duplicates. Keep under 170 words. Feature: {{details}}

Diagnose low conversion: segment by channel/device, check speed, messaging mismatch, and UX friction. Provide 5 tests. Keep under 170 words. Funnel: {{details}}

Plan to declutter a dashboard: remove unused charts, group sections, add context, and alerts. Keep under 150 words.

Write an SLA for data requests: tiers, response times, intake form, and escalation. Keep under 170 words.

Structure an experiment readout: hypothesis, results, interpretation, decision, and follow-ups. Keep under 170 words. Experiment: {{details}}

Prioritize data debt items: impact on decisions, frequency, effort, and owner. Return ranked list with actions. Keep under 180 words. Items: {{paste}}

Create a weekly metrics report template: highlights, lowlights, risks, and next actions. Keep under 150 words.

List key questions to pressure-test attribution results and data quality. Keep under 140 words.

Write a data dictionary entry: field name, definition, type, allowed values, source, and owner. Keep under 120 words. Field: {{field}}

Create a self-serve analytics guide: how to find data, trusted sources, and when to ask for help. Keep under 170 words.

Design alerts for {{metric}}: thresholds, channels, on-call rules, and runbook link. Keep under 160 words.

Give visualization tips for {{dataset}}: chart choice, labeling, color usage, and accessibility. Keep under 170 words.

Audit a metric: definition, owners, usage, dashboards, and data quality. Recommend fixes. Keep under 170 words. Metric: {{metric}}

Create a data review meeting agenda: goals, prep materials, decisions needed, and follow-up tracking. Keep under 140 words.

Map an automation for {{process}}: trigger, inputs, actions, outputs, and failure alerts. Keep under 170 words.

Provide an RPA build checklist: selectors, retries, idempotency, logging, and exception paths. Keep under 160 words.

Suggest 10 automation ideas for {{team}} sorted by impact/effort. Keep each under 16 words.

Write a workflow spec: trigger, pre-checks, steps, error handling, retries, and owner. Keep under 180 words. Workflow: {{details}}

Plan an integration: auth, rate limits, pagination, retries, and monitoring. Keep under 170 words. Systems: {{details}}

Reduce alert fatigue: deduplicate, throttle, severity tiers, and actionable criteria. Keep under 150 words. Alerts: {{details}}

Add idempotency to {{workflow}}: keys, safe retries, and side-effect guards. Keep under 150 words.

Create a data sync checklist: scope, mapping, backfill, conflict rules, and monitoring. Keep under 170 words. Sources: {{details}}

Design a webhook flow: event types, auth, retries, signature verification, and docs notes. Keep under 170 words. Events: {{details}}

Automate SLA tracking: timers, alerts, escalation steps, and reporting. Keep under 170 words. SLA: {{details}}

Suggest 10 chatops bot commands for {{team}}. Keep each under 12 words and note needed permissions.

Outline a QA automation plan: test pyramid focus, tools, data seeding, and CI integration. Keep under 180 words.

Recommend retry strategy for {{operation}}: when to retry, backoff, jitter, and max attempts. Keep under 150 words.

Design an approval workflow: approvers, thresholds, SLA, notifications, and audit logging. Keep under 170 words. Request type: {{type}}

Write a health check playbook: what to test, frequency, alert thresholds, and rollback triggers. Keep under 170 words. System: {{system}}

Plan an ETL pipeline: extract cadence, transform rules, load targets, validation, and monitoring. Keep under 180 words. Data: {{details}}

Suggest a scheduling approach for {{job}}: cron hints, concurrency control, and missed-run handling. Keep under 150 words.

Create a playbook for stuck jobs: detection signals, retry rules, manual fix, and prevention. Keep under 170 words.

Plan for API rate limits: detection, queuing, backoff, and customer comms. Keep under 170 words. API: {{details}}

Set up error budget tracking: targets, alert tiers, and throttle rules. Keep under 160 words. Service: {{details}}

Draft a runbook for {{automation}}: inputs, steps, expected outputs, and rollback. Keep under 170 words.

List privacy guardrails for automations: data minimization, masking, access control, and retention. Keep under 170 words.

Define rules for sandbox vs prod automations: data separation, credentials, rollout, and auditing. Keep under 170 words.

Design a human-in-the-loop checkpoint for {{workflow}}: when to pause, what to review, and approve/reject actions. Keep under 170 words.

List automations worth templating for {{team}} with triggers and outputs. Keep under 160 words.

Plan cost monitoring for automations: per-run cost, anomaly alerts, and optimization ideas. Keep under 170 words.

Provide best practices for secrets in automations: storage, rotation, scope, and logging rules. Keep under 150 words.

Create a documentation template for automations: purpose, inputs, steps, dependencies, failure modes, and owner. Keep under 170 words.

Decide between batch vs real-time for {{use case}}: latency needs, volume, consistency, and cost. Keep under 160 words.

Define metrics to track automation health: success rate, latency, retries, cost, and business impact. Keep under 170 words.

Outline a data model for {{domain}}: entities, relationships, key fields, and grain. Keep under 180 words.

Draft a SQL skeleton to answer: {{question}}. Include CTEs for source, cleaning, and aggregation. Keep under 120 words.

Write a data contract: schema, freshness, quality checks, owner, and change process. Keep under 180 words. Table: {{name}}

List quality rules for {{dataset}}: null checks, ranges, uniqueness, referential integrity, and alerts. Keep under 170 words.

Design a dimensional model: fact table grain, dimensions, and sample measures for {{process}}. Keep under 180 words.

Provide PII handling rules: classification, masking, access, and retention for {{dataset}}. Keep under 170 words.

Summarize lineage for {{metric/table}}: sources, transforms, downstream consumers, and owners. Keep under 170 words.

Create validation steps after ETL: row counts, key checks, null diffs, and sampling queries. Keep under 150 words.

Plan a schema change: backfill, dual-write/dual-read, deprecation timeline, and communication. Keep under 180 words. Change: {{details}}

Suggest indexes for these queries with reasoning. Flag over-indexing risks. Keep under 170 words. Queries: {{paste}}

Draft a governance charter: roles, standards, review cadence, and tooling for {{organization}}. Keep under 180 words.

Audit warehouse costs: heavy queries, cold data, storage, and optimization ideas. Keep under 170 words. Warehouse: {{details}}

Outline Change Data Capture for {{system}}: source, capture method, ordering, and conflict handling. Keep under 180 words.

Recommend a sampling strategy for {{dataset}}: method, size, and bias checks. Keep under 150 words.

Design a time-series storage plan: granularity, retention, rollups, and partitioning. Keep under 170 words. Metric: {{metric}}

Write a data sharing policy: permissible uses, approvals, anonymization rules, and logging. Keep under 170 words.

Draft a BI dashboard spec: audience, KPIs, filters, drill paths, and refresh cadence. Keep under 170 words.

Provide a migration checklist: schema mapping, data validation, cutover plan, and rollback. Keep under 170 words. Migration: {{details}}

Suggest optimizations for this SQL: indexes, CTE/materialization, filters, and avoiding scans. Keep under 170 words. Query: {{paste}}

Create an access request template: purpose, data needed, duration, safeguards, and approvals. Keep under 150 words.

Map KPIs to tables/fields needed. Include joins and filters. Keep under 180 words. KPIs: {{paste}}

Plan a null analysis: fields to check, distributions, and cleanup actions for {{dataset}}. Keep under 170 words.

Write a catalog entry: description, fields, freshness, owner, upstream/downstream tables, and caveats. Keep under 170 words. Table: {{name}}

Define late data handling for {{pipeline}}: acceptable delay, backfill rules, and alerts. Keep under 170 words.

Propose an access model: roles, permissions, audit logging, and request flow. Keep under 170 words.

Suggest data tests for {{table}}: schema, uniqueness, accepted values, freshness, and volume. Keep under 160 words.

Create a plan to reconcile metric mismatches between systems: assumptions, alignment steps, and monitoring. Keep under 180 words. Metrics: {{details}}

Write a retention plan: what to delete/retain, timelines, legal holds, and automation. Keep under 170 words.

Draft a data incident template: scope, impact, affected tables, fix, and prevention. Keep under 170 words.

Propose metadata to collect for {{dataset}}: lineage, owners, quality scores, and SLAs. Keep under 170 words.

Create an SOP template: purpose, scope, prerequisites, steps, safety checks, and escalation. Keep under 170 words. Process: {{process}}

Outline incident roles (IC, comms, ops), timelines, and update cadence for {{severity}} incidents. Keep under 170 words.

Make a runbook index: common incidents, owner, link placeholder, and last review date. Keep under 170 words.

Draft a capacity plan: demand forecast, constraints, hiring/contract options, and risk mitigations. Keep under 180 words. Team: {{team}}

Create a vendor evaluation scorecard: criteria, weights, red flags, and decision format. Keep under 170 words. Need: {{details}}

Design a change calendar: required fields, blackout windows, approvals, and notification rules. Keep under 170 words.

Write a service catalog entry: description, owner, SLA, dependencies, and support path. Keep under 150 words. Service: {{service}}

Create an onboarding checklist for {{role}}: access, training, docs, shadowing, and first-week goals. Keep under 170 words.

List offboarding steps: access removal, knowledge capture, equipment, and exit interview prompts. Keep under 150 words.

Outline a business continuity plan: critical systems, RPO/RTO targets, backups, and testing cadence. Keep under 180 words.

Build an escalation matrix: tiers, contacts, response times, and criteria for escalation. Keep under 170 words.

Create a shift handoff template: status, incidents, tasks, risks, and pending approvals. Keep under 150 words.

Plan inventory management: min/max levels, reorder triggers, audits, and supplier backups. Keep under 170 words. Items: {{details}}

Outline a policy rollout: stakeholders, training, compliance checks, and feedback loop. Keep under 160 words. Policy: {{policy}}

Draft a contract playbook: fallback clauses, approval matrix, redline limits, and signature process. Keep under 180 words.

List core ops metrics for {{team}} with definitions and targets. Keep under 170 words.

Set a review cadence for SOPs: frequency, owner, versioning, and change log steps. Keep under 150 words.

Write a post-incident review template: summary, root cause, impact, fixes, and follow-ups with owners. Keep under 180 words.

Create a facilities checklist: safety, access control, maintenance schedule, and vendor contacts. Keep under 170 words.

Draft a travel policy: booking rules, per diems, approvals, and reimbursement steps. Keep under 170 words.

Design OKR rituals: planning, mid-quarter check, retrospective, and dashboards. Keep under 170 words.

Create a vendor handoff doc: contacts, SLAs, access, billing, and escalation. Keep under 150 words.

Write a change freeze notice: dates, scope, exceptions, and contact info. Keep under 100 words.

Provide an audit prep checklist: documents, access, evidence storage, and timeline. Keep under 170 words. Audit type: {{type}}

Draft an escalation email: issue summary, impact, attempted fixes, and requested action. Keep under 110 words. Issue: {{details}}

Align budget to capacity plan: cost per seat, tools, contractors, and contingency. Keep under 170 words. Team: {{team}}

Create a training plan for {{process}}: objectives, modules, hands-on practice, and assessment. Keep under 170 words.

Build a risk mitigation matrix: risk, likelihood, impact, owner, and mitigation steps. Keep under 170 words. Context: {{details}}

Summarize operations run rate: major cost buckets, trends, and savings ideas. Keep under 170 words.

Create a vendor renewal checklist: performance, usage, pricing changes, security review, and negotiation levers. Keep under 170 words.

Summarize budget for {{team}}: planned vs actual, variance highlights, and top drivers. Keep under 170 words.

Outline a forecast: assumptions, revenue streams, cost buckets, scenarios, and update cadence. Keep under 180 words.

Calculate unit economics for {{product}}: CAC, payback, LTV, gross margin, and sensitivity levers. Keep under 180 words.

Provide a cash flow checklist: inflow/outflow timing, reserves, receivable follow-ups, and burn multiples. Keep under 170 words.

Analyze pricing options: tiered vs usage vs seat, margin impact, and risks. Keep under 180 words. Context: {{details}}

Explain budget variance: top deltas, causes, recurring vs one-time, and corrective actions. Keep under 170 words. Data: {{paste}}

Draft an expense policy: allowed categories, limits, approval flow, receipts, and reimbursement timing. Keep under 180 words.

List 10 cost reduction ideas for {{team}} with expected impact and risk. Keep each under 18 words.

Write a collections playbook: dunning cadence, messaging tone, escalation, and incentives. Keep under 170 words.

Clarify CapEx vs OpEx treatment for {{purchase}} with accounting note and approval steps. Keep under 150 words.

Outline a board finance pack: P&L highlights, cash runway, KPIs, hiring, and risks. Keep under 180 words.

Summarize revenue recognition approach for {{model}}: performance obligations, timing, and edge cases. Keep under 180 words.

Build a scenario summary: base/bull/bear for revenue and costs with triggers. Keep under 170 words. Assumptions: {{details}}

Draft a headcount plan: roles, timing, cost per hire, and dependencies. Keep under 170 words. Goal: {{goal}}

Write a billing error response: apology, fix steps, timeline, and goodwill gesture if appropriate. Keep under 110 words. Issue: {{details}}

Provide a procurement checklist: vendor vetting, security review, pricing, legal terms, and approvals. Keep under 170 words.

Outline an ROI calculator: inputs, formulas, assumptions, and outputs for {{product}}. Keep under 170 words.

Suggest ways to extend runway: cost cuts, pricing moves, collections, or financing. Keep under 170 words. Current runway: {{months}} months.

Set budget guardrails: spend thresholds, approval limits, and monitoring cadence for {{team}}. Keep under 160 words.

Provide negotiation levers: term, volume, payment timing, SLAs, and references. Draft 3 ask emails. Keep under 180 words.

Forecast expenses for {{category}} with seasonality notes and cost-saving suggestions. Keep under 170 words.

Align financial KPIs to strategy: revenue growth, margin, CAC payback, and cash runway. Keep under 170 words.

Provide a month-end close checklist: reconciliations, accruals, revenue checks, and reporting. Keep under 170 words.

Summarize cap table: ownership by class, dilution impacts, and option pool status. Keep under 170 words. Data: {{paste}}

Craft a fundraising story: market, traction, moat, plan for funds, and milestones. Keep under 180 words.

Define expense approval matrix: thresholds, approvers, documentation, and audit trail. Keep under 150 words.

Write payment terms policy: standard terms, early pay discounts, late fee rules, and negotiation guardrails. Keep under 170 words.

Create an internal finance FAQ: invoicing, reimbursements, cards, and approvals. Keep under 180 words.

Plan audit trails for payments: fields to log, retention, and review cadence. Keep under 160 words.

Define a SaaS metrics dashboard: MRR, churn, expansion, payback, and rule-of-40. Keep under 170 words.

Draft a job description for {{role}}: mission, impact, key responsibilities, requirements, and 90-day expectations. Keep under 200 words.

Create an interview plan: stages, focus areas, interviewers, and time per stage. Keep under 170 words. Role: {{role}}

Build a scorecard: competencies, evidence to seek, rating scale, and must-have/avoid signals. Keep under 170 words. Role: {{role}}

Provide 10 interview questions for {{role}} covering skills, behaviors, and culture add. Include what good looks like. Keep under 200 words.

Write a sourcing message: personalized opener, role hook, impact, and call to chat. Keep under 90 words. Candidate: {{details}}

Draft a take-home assignment brief: goal, deliverables, time limit, evaluation criteria, and submission format. Keep under 180 words. Role: {{role}}

Create a rubric for {{skill}}: beginner/intermediate/advanced descriptors and evidence to look for. Keep under 180 words.

Prepare a panel: panel mix, focus for each interviewer, and anti-bias reminders. Keep under 150 words. Role: {{role}}

Write an email setting expectations: stages, timelines, and what to prepare. Keep under 110 words. Role: {{role}}

Draft a referral ask to teammates: role summary, ideal profile, and how to refer. Keep under 90 words.

Review this JD for inclusive language, jargon, and must-have inflation. Suggest fixes. Keep under 170 words. JD: {{paste}}

List 8 background questions to validate experience and outcomes for {{role}}. Include what good answers show. Keep under 170 words.

Write a hiring manager brief: role mission, top 3 skills, culture adds, and interview focus. Keep under 170 words. Role: {{role}}

Create a debrief template: signal summary, concerns, hire/no-hire vote, and rationale. Keep under 120 words.

Outline an offer letter: role, comp, equity, start date, contingencies, and response deadline. Keep under 170 words.

Plan how to close a candidate: motivation map, tailored value props, references, and timeline. Keep under 170 words. Candidate: {{details}}

Write a kind rejection email with appreciation, brief reason, and invite to reapply if appropriate. Keep under 100 words.

Suggest 8 diversity-focused sourcing ideas for {{role}}. Keep each under 18 words.

Create an interviewer training outline: bias reminders, legal boundaries, question design, and note-taking. Keep under 180 words.

Assess pipeline health: stage conversion, time-in-stage, and bottlenecks. Suggest fixes. Keep under 170 words. Data: {{paste}}

Outline candidate research steps: resume scan, portfolio highlights, and tailored questions. Keep under 150 words. Candidate: {{details}}

Create a structured interview kit: intro script, 6 questions with scoring notes, and wrap-up. Keep under 180 words. Role: {{role}}

Draft a background check policy: when to run, scope, consent, and adverse action steps. Keep under 180 words.

Propose compensation bands for {{role}}: levels, salary range, equity range, and rationale. Keep under 180 words.

Create a 30/60/90 onboarding plan: goals, relationships, training, and success signals. Keep under 180 words. Role: {{role}}

Write an email confirming interview logistics: date/time, format, prep tips, and interviewer names. Keep under 110 words.

Draft an agency brief: role summary, must-haves, nice-to-haves, process, and SLA. Keep under 170 words.

Suggest 8 employer brand post ideas highlighting culture, growth, and impact. Keep each under 20 words.

Create an interview debrief agenda: candidate summary, signal review, disagreements, and decision. Keep under 150 words.

Provide an offer negotiation guide: what to learn, flexibility ranges, trade-offs, and when to walk. Keep under 170 words.