Outcome-First Codex Task Writer for a Feature or Bug Request
Turns a raw feature or bug request into a paste-ready Codex task with a goal, constraints, files in scope, definition of done and exact verification commands.
341 prompts · last added
249 results for “definition-of-done” · page 1 of 11
Turns a raw feature or bug request into a paste-ready Codex task with a goal, constraints, files in scope, definition of done and exact verification commands.
Has Claude Code define schema-based handoff contracts between agent phases, generate a validator, and add contract tests. Supports the decision of which phase boundaries need strict contracts versus lightweight checks.
Turns pasted customer reviews into evidence-based personas, jobs-to-be-done, objections and a bank of exact customer phrases ready to reuse in copy.
Guides Codex through reproducing a failing CI job locally, classifying the cause as code, test, environment, or flaky, applying a minimal fix when safe, and producing an evidence-based handoff for anything it cannot resolve.
Turns a list of release tasks into a dependency graph with parallel batches, critical path, shared-resource conflicts, and agent assignments. Supports the decision on what to run now versus wait on.
Designs the handoff contracts, stop conditions, and review gates for a sequential chain such as researcher, writer, editor, and fact-checker. Helps you decide whether the chain is ready to run.
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.
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.
Designs a three-agent content pipeline where a researcher, writer and editor pass structured handoffs, with the exact fields each agent receives and returns and checks between stages.
Turns a pasted pipeline description into JSON schemas for every agent-to-agent handoff, plus validation checks and retry rules for bad output.
Writes a verified handoff file covering changes, decisions, open issues and next steps so a new Claude Code session can continue without re-reading the whole history.
Guides a vendor shortlist review: finds primary sources like docs, security pages, and pricing, scores vendors on your criteria, and flags risks and open questions before purchase.
A five-minute end-of-day check that records what got done, captures loose ends, and picks three priorities for tomorrow so you can stop thinking about work.
Produces a developer-ready component specification covering anatomy, variants, states, tokens, accessibility, and open questions from a short component brief.
Builds a negotiation script for a job offer: your anchor number with a reason, word-for-word replies to common pushback, and a walk-away line, using market data you supply.
Turn your job offer and target number into a polite counteroffer email, phone talking points and replies to the three likeliest pushbacks.
Compare the avalanche and snowball methods on months to debt-free and total interest using your own debts and extra payment, as education only.
Plans 30 days of posts that lead to one offer: content pillars, a mix of value, proof and ask posts, hooks for each day, and the platform and format to use.
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.
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.
Builds a blog post outline for one keyword by first deciding the search intent, then structuring headings, questions and examples that match what searchers expect to find.
Turns a list of links and your quick takes into a readable newsletter issue with a subject line, an opening, short summaries and your own angle on each item.
Edits stock phrases, forced triads, em-dash habits and hype words out of an AI-assisted draft while keeping your meaning and voice, with a change log.
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.
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.