Interview Me Then Plan: Requirements Interview Before Any Code
Claude Code questions you about a feature's requirements and edge cases, then delivers an implementation plan with acceptance criteria and test commands, without writing code first.
341 prompts · last added
151 results for “surrounded by” · page 4 of 7
Claude Code questions you about a feature's requirements and edge cases, then delivers an implementation plan with acceptance criteria and test commands, without writing code first.
Stress-tests a plan with five strong objections, hidden assumptions, the likeliest failure path and the evidence that would change the verdict.
Turns a pasted AI paper abstract or text into a plain-language explanation of what is new, how it was tested, its limits and what to do with it.
Audits an existing multi-agent pipeline for failure modes and produces retry limits, fallback paths, escalation triggers, and a test plan. Supports the decision on what to harden before wider rollout.
Splits a research question across parallel research agents, defines source discovery and evidence review steps, merges findings into a citation table, and produces a decision memo without claiming live browsing.
Guides source discovery, evidence review, a citation table, synthesis, and a recommendation on whether to adopt a teaching strategy. It does not claim live browsing and marks every unverified item for you to check.
Builds a tailored discovery call agenda, question bank, and qualification scorecard so a rep can decide whether to advance, nurture, or disqualify an opportunity after the call.
Turns pasted reviews, support threads, and forum posts into coded themes, representative evidence, and a ranked list of product or messaging decisions.
Designs verification checks, error handling, and a self-correction loop for an agent task before it runs, based on likely failure modes.
Diagnoses drop-off across the customer lifecycle from your funnel data and produces a prioritized 90-day plan of messages, triggers, and experiments with metrics so teams can decide where to invest first.
Turns your product facts, customer evidence, and competitor notes into a tested positioning statement, messaging hierarchy, and proof-gap list so a marketing team can decide what to say and what to validate first.
Tests a specific claim or statistic against primary and peer-reviewed sources. Produces an evidence grid, a contradiction log, and a calibrated confidence rating with explicit unknowns.
Produces a developer-ready component specification covering anatomy, variants, states, tokens, accessibility, and open questions from a short component brief.
Audits a user flow from screenshots or descriptions and returns an evidence-labeled issue table plus a fix-now, next, defer plan for a sprint decision.
Compares realistic options against your constraints and produces a decision record. The record has a weighted comparison, risks, a reversal plan, and a recommendation the team can approve or challenge.
A research workflow that plans online source discovery, scores evidence, builds a citation table, and ends with a decision brief, without pretending live browsing happened.
Audits an existing or planned onboarding email flow, then rewrites it around a single activation event with segmentation, timing, copy, and a measurement plan.
Turns current pricing, cost, and customer data into a decision memo comparing hold, adjust, and repackage options, with scenario math, risks, and a controlled pricing test plan.
Produce a decision memo that compares pricing options using your numbers, with scenario math, customer risk, and a test plan. Helps a founder or manager decide whether to change prices and how.
Build a research plan that shows where to find competitor evidence, how to judge sources, and how to log citations. It never claims live browsing happened, so you can verify each source yourself.
Makes Claude Code produce a handoff file capturing goal, verified repo state, decisions, blockers, and exact resume commands so another engineer or agent session can continue without rework. Use it before ending a long task.
Has Codex review a branch diff against a base ref in read-only mode. It checks correctness, tests, security, and maintainability, and returns evidence-backed findings with severity and a merge recommendation.
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.
Maps a current team workflow, finds bottlenecks and handoff failures, designs a leaner future-state process with roles and automation candidates, and outlines a low-risk pilot with success metrics.
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.