Team playbook for Claude Code and Cursor
An engineering team shares a playbook: research before coding, plan mode, phased commits, and 3–5 parallel Claude Code sessions in git worktrees.
- Agent or tool
- Claude Code
- Topic
- Software Development
- Reported on
- Added
- 2026-10-15
Why it matters
Coding agents are moving from autocomplete to doing whole tasks: reading a codebase, making a plan and changing many files. This case is a concrete example of where that works in practice. It is one of 221 sightings filed under Software Development on Agent Sightings (number 135 by interest), and one of 255 involving Claude Code.
How you could try it
Here is a reusable prompt, written by us in our own words, that captures the task. Paste it into Claude Code or any similar agent and adjust the details to your situation.
Before writing code, research the architecture in plan mode. Outline phases. Implement phase 1 only, then pause for review and commit before continuing.
The prompt breaks down into 3 steps you can check as the agent works:
- Before writing code, research the architecture in plan mode.
- Outline phases.
- Implement phase 1 only, then pause for review and commit before continuing.
Tip: Work on a fresh branch, ask for a plan before edits, and review the diff and test results before merging.
Source
Read the original first-hand account on Reddit: https://www.reddit.com/r/ClaudeAI/comments/1ppxvgv/how_we_use_claude_code_and_c…. Our summary is a paraphrase; details are in the source.
Built an AI agent? Feature your agent on Agent Sightings, free submission or a featured spot.
Browse more like this
Related sightings
- A contractor's personal Claude Code agent allegedly ran inside a secure Pentagon system for two months
- Claude Code's 3-word status line reportedly burns 15 to 20% of tokens
- Office Hours: Asynchronous coding and the end of the IDE with Spotify
- Rocket Money on building agents that fix their own code
- Book the best-priced flight and later refund it
- Build a DIY slide tower with a subagent