- AI Coding Agents
- Agent
- Intermediate
- Claude Code
- Published
Claude Code Repo Recon and Implementation Plan for a New Feature
Has Claude Code inspect a repository read-only and produce an evidence-based implementation plan with file-level changes, tests, risks, and open questions. Use it to decide whether to start, split, or clarify a feature before any code is written.
You get: Job-to-be-done and decision supported, verified findings and proposed change plan
The prompt
mkdir -p .agents/skills/claude-code-repo-recon-and-implementation-plan-for-a-new-feature && curl -sL "https://prompts-gpt.com/prompts/claude-code-repo-recon-and-implementation-plan-for-a-new-feature/raw" -o .agents/skills/claude-code-repo-recon-and-implementation-plan-for-a-new-feature/SKILL.mdTips and common edits
Run in Claude Code plan mode or with edit permissions denied. Add repo-specific rules to CLAUDE.md first for better results. After approving the plan, start a fresh session to implement one step at a time.
Questions about this prompt
More like this
More in AI Coding AgentsAgent Session Handoff Brief with Resume Checklist and Verified State
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.
Characterization-Test-Backed Refactor with Incremental Commits
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.
Pre-Merge Self-Review of a Git Diff: Correctness, Security, and Test Gaps
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.
Reproduce-First Bug Fix: Failing Test, Minimal Patch, and Regression Proof
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.
Claude Code Plan-Then-Implement a Feature With Approval Checkpoints
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.
Interview Me Then Plan: Requirements Interview Before Any Code
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.
Agent Run Post-Mortem: Trace Root Cause and Prompt or Tool Fixes
Analyzes a pasted agent trace to find the first real failure and proposes exact prompt rewrites or tool changes, each with a test.
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.
Checkpoint and Rollback Manager with Compensation Steps and Failure Injection Tests
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.
Claude Code Behavior-Preserving Refactor with Characterization Tests and Staged Commits
Guides Claude Code to refactor a module safely by first pinning current behavior with characterization tests, then applying small reversible steps with verification after each. Delivers a diff, risk register, and rollback plan.
Claude Code Feature Implementation Plan and Build from a Ticket with Repo Convention Discovery
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.
Claude Code Hook Writer: Auto-Run Lint, Typecheck or Tests After Edits
Produces a PostToolUse hook entry for settings.json, the script it calls and a concrete procedure to test that the check runs after file edits.