Plan Before Edit: Cursor Plan-Mode Prompt for a Feature Request
Produces a read-only Cursor plan listing files in scope, ordered steps, specific risks and tests to run before any code is changed.
You get: Working code with an explanation
The prompt
mkdir -p .agents/skills/plan-before-edit-cursor-plan-mode-prompt-for-a-feature-request && curl -sL "https://prompts-gpt.com/prompts/plan-before-edit-cursor-plan-mode-prompt-for-a-feature-request/raw" -o .agents/skills/plan-before-edit-cursor-plan-mode-prompt-for-a-feature-request/SKILL.mdAct as a senior engineer in Cursor plan mode. Do not edit, create or delete any files. Use read-only exploration only.
Feature request: {describe your feature request}
Search the codebase to find where this feature belongs, which existing patterns to follow, and how tests are set up. If behavior or scope is ambiguous, ask me one or two short questions before planning.
Rules:
- List only files you have confirmed exist, and label each as modify, create or read-only reference with a one-line reason.
- Order the steps so each is small, independently verifiable, and names the files it touches.
- Make risks specific to this code (shared utilities, migrations, public APIs, flaky tests) and give each a mitigation.
- Use the repo's real test commands, name any new tests to write, and say which to run before and after each step.
Output exactly:
1. Goal and assumptions
2. Files in scope (table: path, action, reason)
3. Ordered steps (numbered checklist)
4. Risks and mitigations
5. Tests to run (baseline first)
6. Open questions
End by asking me to approve the plan before any code changes.Example output
Tips and common edits
Use at the start of a feature in Cursor plan mode with the repo open. Replace the variable with a one- to three-sentence description of the feature.
Questions about this prompt
More like this
More in CursorCoding 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.
Cursor Characterization-Test-First Refactor of a Legacy Module
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.
Characterization Tests Before a Refactor
Writes tests that lock in a module's current behavior, including edge cases and quirks, so you can refactor safely.
Codebase Tour for a Specific Task
Explores a repo through the lens of your task and explains the architecture, key files and data flow, then says where to start.
Cursor Agent Bug Triage: Reproduce, Root-Cause, Fix, and Regression Test
Guides Cursor Agent through reproducing a bug, isolating the root cause with evidence, applying a minimal diff, and adding a regression test, ending with a verification checklist and risks.
Cursor Incremental Dependency Migration Plan and Codemod Execution
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.
Cursor Project Rules Generator for Your Repo's Stack
Has Cursor inspect your repository and write 3-5 scoped .mdc rules, each with globs, a description and a deliberately chosen attach mode.
Cursor Refactor of a Component With Zero Behaviour Change
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.
Dependency Graph Planner for a Multi-Agent Software Release Workflow
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.
Edge-Case Test Suite for One Function in Your Existing Test Framework
Writes tests for a single function that cover normal inputs, boundaries, bad input and error paths, in the test framework your project already uses.
Failing Test First Bug Fix
Reproduces a bug with a failing test, finds the root cause, applies the smallest fix and shows the test passing.
Pull Request Review with Merge Recommendation
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.