Eight-Objection Handling Playbook: Acknowledge, Ask, Reframe, Evidence
Builds a playbook that answers the eight most likely objections for your product and buyer, each in four steps with honest evidence.
341 prompts · last added
276 results for “Each mark is a simple” · page 7 of 12
Builds a playbook that answers the eight most likely objections for your product and buyer, each in four steps with honest evidence.
Tightens an overlong text by about 30 percent without losing meaning, then lists what was cut and why.
Has Claude Code review a branch diff like a skeptical maintainer, producing severity-ranked findings with evidence and a clear merge, fix, or block recommendation. Use it before opening or approving a pull request.
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then making small, reversible commits. Helps you decide whether the refactor preserved behavior and is worth merging.
Converts discovery notes into a one-page proposal executive summary and a dated mutual action plan. It helps a rep decide whether the deal is ready to propose and what is still missing.
Runs a behavior-preserving refactor in Codex exec. It pins current behavior with characterization tests, refactors in small verified steps inside an allowed scope, and ends with an evidence-based handoff for the merge decision.
Guides Claude Code to build or refactor a dependency-aware DAG scheduler for agent phases, with cycle validation, bounded parallelism, join policies, retries, and an append-only run ledger so interrupted runs resume without redoing finished nodes.
Writes a 250-word cover letter that picks the employer's top three needs from the job post and answers each with a specific example from your resume.
Turns your common support questions and policies into ten reusable reply macros with a warm tone, the right policy detail, and a placeholder only where agents must personalise.
Builds a one-page cheat sheet of your ten most likely sales objections, each with the real concern behind it, a question to ask back, a short answer, and proof to share.
Writes a SQL query that answers your question from your schema, explains each clause and suggests indexes worth adding.
Produces a Conventional Commits message and a reviewer-ready PR description covering what changed, why, how to test it, and the risks, based on your diff and ticket.
Audits an old article for outdated facts and missing subtopics, proposes new sections and rewrites the intro for your target keyword.
Produces a 3-5 subagent roster with system prompts, minimal tool permissions, model tiers and explicit handoff rules for your project.
Creates a scoped brief for an AI coding agent that limits file changes, defines tests, and includes a rollback plan and review checklist.
Plans and executes a library or framework version migration in Cursor in small, verifiable batches, with an impact inventory, rollback points, and per-batch test gates instead of one risky bulk edit.
Runs a read-only Codex investigation that maps the relevant code paths, test commands, and likely root causes for a bug report. It ends with a ranked hypothesis table and a go/no-go recommendation before any edits.
Checks a claim you saw online against primary sources, traces where it came from, and returns a verdict with a confidence rating and the evidence on both sides.
Matches your existing resume to one job description: keyword gap table, rewritten bullets that use only your real experience, and a list of requirements you cannot honestly claim.
Turns an unsorted list of tasks, errands and worries into a realistic week of time blocks, with the hardest work placed in your best hours.
Turns a rough prompt into a structured one with role, context, task, constraints and output format, plus a one-line reason for each change.
Scores your essay criterion by criterion against your rubric and names the three fixes that will improve it most, without rewriting anything.
Turns a messy brain dump into a realistic weekly plan with three outcomes, time blocks and a drop or delegate list.
Directs Claude Code to reproduce a reported bug with a failing test, apply the smallest fix, and prove the fix with command output. Use it to decide whether a bug is fixed and safe to merge.
Guide
Nothing that fits? Write a prompt with AI.
341 copy-ready prompts for productivity, writing, business and coding and more. Each one sets the role, the steps and the output format, and marks the parts you fill in with curly brackets.
Most are written for ChatGPT (285), Gemini (260), Claude (217) and Claude Code (42); the number is how many prompts list that tool. Each prompt page lists its tools, and most text prompts also work in any capable chat model.
Words in curly brackets, such as {audience}, are the parts you replace with your own details. Choose “Ready to use (no blanks)” in the filters to see prompts you can paste as they are.
By how often they are copied, unless you choose another order. Newest shows the latest additions first. Trending ranks prompts by copies, opens and saves over the last two weeks.
No. Every prompt is free to copy or open in your AI tool. A free account lets you save prompts to your vault.
Yes. Write with AI asks what you need, builds a short form for it, and writes the prompt as you fill it in.