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
118 results for “performance-review” · page 3 of 5
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.
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.
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.
Audits an existing or planned onboarding email flow, then rewrites it around a single activation event with segmentation, timing, copy, and a measurement plan.
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.
Summarizes an uploaded long video or PDF with timestamp or page citations, then lists key claims with evidence and action items.
Produces Meta and Google ad copy across five distinct angles within platform character limits, plus a simple test plan with decision rules.
Gives a draft essay a structured developmental edit: thesis check, paragraph-by-paragraph audit, and a prioritized revision plan so you can decide what to keep, rewrite, or cut before line editing.
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.
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.
Creates a same-day recap email and a three-touch re-engagement sequence from meeting notes. It helps a rep confirm commitments and decide whether a quiet deal should be chased, reframed, or closed out.
Turns pasted account material and a source discovery plan into a evidence-labeled research brief. It helps a rep decide whether to pursue an account, which persona to target, and which outreach angle to use.
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.
Generates a set of testable hook variants and a measurement plan for a vertical video so a creator can decide which version to publish first and what to learn from results.
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.
Guides a source-backed evaluation of software or service vendors against weighted criteria. Ends with a decision memo covering risks, open questions, and verification steps before purchase.
Has Cursor lock in current behavior with characterization tests before restructuring a legacy module in small steps, so you can decide whether the refactor preserved behavior and is safe to merge.
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.
Builds a behavior-based test matrix for a function or module and then generates test code in your framework. Covers edge cases, failures, and mocking boundaries, with coverage gaps stated honestly.
Create a writer-ready content brief from SERP observations you supply. It covers intent, required sections, evidence gaps, and a go or no-go call on whether the page is worth producing.
Turn a crawl export and Search Console data into a scored, sprint-ready technical SEO fix list. It separates facts from assumptions and flags what needs verification before developers start work.
Turns rough notes and supplied source excerpts into a send-ready newsletter issue. It compares lead angles, flags unsupported claims, and ends with a go/no-go checklist before you hit send.
Plan a custom GPT before building it. Produces the instruction text, knowledge file plan, conversation starters, and a test set so you can decide whether to build, narrow, or skip it.
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.