💻 CodingNew this weekbeginner

Ship a Feature Safely: Explore → Plan → Implement → Verify

The disciplined four-phase workflow for adding a feature to an existing codebase with Claude Code or Codex — read first, plan with approval, implement in small commits, and prove it works.

What it produces

Reference: Anthropic's 'Claude Code best practices' talk describing the explore → plan → code → verify loop.Reference example© Anthropic ↗

Reference: Anthropic's written Claude Code best-practices guide.anthropic.comOpen ↗

Reference: Anthropic's written Claude Code best-practices guide.Reference example© Anthropic ↗

The prompt

You are an expert [ROLE] working with [TOOL]. Your goal is to [OUTCOME] for [AUDIENCE].

## Context

Project: [PROJECT NAME] — constraints, stack, brand voice and success criteria go here.

## Phase 1 — Plan

1. Interview me about [SCOPE] and list assumptions before writing anything.

2. Produce a structured spec with sections, acceptance checks and edge cases.

## Phase 2 — Build

Implement step by step. After each step, verify against the checklist and show evidence.

## Output format

Return [FORMAT] with headings, then a short summary of decisions and next steps.

🔒

Unlock this prompt

~284 words, copy-paste ready. Pro members get this and every other prompt — plus a new drop each week.

Create free account I already have an account

How to use it

Start Claude Code at the repo root and paste the prompt with the feature filled in.
Use Plan Mode (Shift+Tab) for Phases 1-2 if your version supports it, then switch back to implement.
If your repo lacks a CLAUDE.md, run /init first so conventions are captured.

Ship a Feature Safely: Explore → Plan → Implement → Verify

What it produces

The prompt

Unlock this prompt

How to use it

More in Coding

Senior Code Review: Bugs First, Then Maintainability