Coding Agent Task Brief with Guardrails, Test Plan, and Rollback Steps
Creates a scoped brief for an AI coding agent that limits file changes, defines tests, and includes a rollback plan and review checklist.
341 prompts · last added
79 results for “looking up or pausing” · page 3 of 4
Creates a scoped brief for an AI coding agent that limits file changes, defines tests, and includes a rollback plan and review checklist.
Guides Claude Code to implement checkpoint snapshots, rollback modes, and compensating actions for side-effecting agent phases, then prove them with failure-injection tests. Helps you decide the rollback strategy per phase.
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 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.
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.
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 GitHub Copilot agent mode to inspect the repository, state assumptions, plan a minimal change, implement it, and add tests. It ends with a verification report you can use to decide whether to open a PR.
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.
Turns an agent idea into a build-ready design: the job, the tools with their inputs and permissions, guardrails, failure handling and a set of evaluation cases to test it.
A SKILL.md that forces your coding agent to reproduce a bug with a failing test before changing code, apply the smallest fix, and prove it with the test suite.
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.
Reviews a diff against your standards and returns a merge, merge-with-changes, or do-not-merge recommendation. Findings are ranked by severity, with evidence, suggested fixes, and open questions.
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.
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.
Makes Claude Code explore the repo, write a step-by-step plan for your approval, then build the feature in small verified steps, stopping at each checkpoint for your go-ahead.
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.
Has GitHub Copilot review your branch diff against the base branch, flag defects and missing tests, and draft a PR description with evidence. Use it to decide whether to open the PR or fix issues first.
Produces an onboarding guide for one folder of a codebase: what it does, how data moves through it, the files to read first and the traps a new developer should avoid.
Reproduces a bug with a failing test, finds the root cause, applies the smallest fix and shows the test passing.
A SKILL.md that makes Claude write and edit in your brand's voice: it reads a VOICE.md in the project, or builds one from samples, then checks every draft against it.
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.
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.
Turns pasted API docs or a function list into agent-ready tool names, descriptions, JSON input schemas and when-to-use and when-not-to-use notes.
Has Codex review a pull request and return comments sorted into blocking, should-fix and nit, each with the file and line, the risk, and a suggested change.
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.