Subagent Fan-Out Plan for a Large Codebase Migration
Plans a big migration so an orchestrating agent can split it into independent chunks for parallel subagents, each with a clear brief, a verification command and merge rules.
341 prompts · last added
276 results for “stockings on the mantel” · page 3 of 12
Plans a big migration so an orchestrating agent can split it into independent chunks for parallel subagents, each with a clear brief, a verification command and merge rules.
Helps you choose between options such as job offers or cities by naming what matters, weighting it, scoring each option, and testing the result against your gut.
Extracts decisions, owned and dated action items and open questions from meeting notes, then drafts a follow-up email.
Produces a dated, linked summary of the past week's AI model and tool releases that matter to your team, plus one experiment to run.
Summarizes an uploaded long video or PDF with timestamp or page citations, then lists key claims with evidence and action items.
Stress-tests a plan with five strong objections, hidden assumptions, the likeliest failure path and the evidence that would change the verdict.
Has the Cursor agent restructure a messy component into smaller pieces while proving the behaviour stays identical, using existing tests or new characterization tests first.
Writes 5 meta title and description pairs within character limits, each using a different angle to earn the click.
Has Codex inspect your repository and write a short, accurate AGENTS.md with the real build, test and lint commands, conventions and boundaries, checked by actually running them.
A ready-to-save SKILL.md that makes your coding agent write Conventional Commits messages and pull request descriptions from the staged diff, never from guesses.
Pulls the central claims out of a long report or paper, with page numbers, the evidence behind each claim and how strong it is, so you can cite or challenge it quickly.
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.
Builds a day-by-day revision calendar that counts back from your exam date, with spaced reviews and timed practice sessions.
Holds a casual conversation at your CEFR level, corrects mistakes inline in brackets, and recaps new vocabulary every 10 turns.
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.
Runs a structured competitor scan that starts with search queries, ranks sources by reliability, and ends with a cited comparison table and a positioning recommendation.
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.
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.
Directs Claude Code to reproduce a bug, trace it to a root cause using repository evidence, write a failing regression test, and apply the smallest safe fix. Ends with a verified diff, risks, and next actions.
Guides Gemini through source discovery, evidence review, a citation table, and a recommendation for choosing between vendors, tools, or technologies. Keeps evidence, inference, contradictions, and open questions separate.
Writes a sincere apology for a mistake at work or in personal life that names what happened, owns the impact, avoids excuses and says what changes next.
Compares products you are choosing between using current reviews and spec sheets, with cited sources, real-world complaints and a recommendation based on how you will use it.
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.
Sorts a pasted bank export into spending categories, shows where the money went, and builds a zero-based budget where every unit of income gets a job.
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.