Fact-Check Research Brief for an Explainer or Documentary Video
Builds a source discovery plan, evidence review, and citation table for a video's factual claims so a producer can decide which claims to keep, soften, or cut before scripting.
341 prompts · last added
56 results for “reflections that were not there” · page 2 of 3
Builds a source discovery plan, evidence review, and citation table for a video's factual claims so a producer can decide which claims to keep, soften, or cut before scripting.
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.
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.
Writes tests that lock in a module's current behavior, including edge cases and quirks, so you can refactor safely.
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.
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.
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.
Produces a least-privilege tool inventory, function definitions, and approval rules for an agent that calls APIs or internal systems.
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.
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.
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.
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.
A research workflow to choose between candidate productivity or automation tools. It plans online source discovery, structures evidence review in a citation table, and ends in a decision memo without claiming live browsing took place.
Builds a transparent market size estimate from discoverable sources, compares top-down and bottom-up methods, and flags weak assumptions before a go or no-go call.
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.
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.
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.
Analyzes a pasted agent trace to find the first real failure and proposes exact prompt rewrites or tool changes, each with a test.
A save-ready SKILL.md that has your coding agent review a branch before merge: correctness, security, tests and migrations, with findings ranked by severity and no style nitpicks.
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.
Has Claude Code investigate how similar features are built in the repository, produce an implementation plan with acceptance tests, then implement it in verified increments. Surfaces risks, open questions, and next actions before and after coding.
Gives codex exec a non-interactive procedure to diagnose a failing CI output, apply a minimal fix, rerun the checks and stop after three attempts with a clear report.
Produces a complete Custom GPT spec with instructions, four conversation starters, a knowledge-file plan, refusal boundaries and a default output format.
Analyzes a recurring manual task and produces an automation blueprint with trigger, steps, data mapping, error handling, and a test plan. It also helps you decide whether the task is worth automating at all.
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.