How to plan agent coding projects
Peter Hartree
Non-trivial coding project? Planning is the most important part. Resist the urge to start building immediately.
Quick tips on planning:
- Mindset: you're a product designer, talking to an engineer. Your job is to make a good plan.1
- Start by telling the agent about your problem—not the thing you think you want to build.
- Ask the agent to brainstorm ways to solve the problem. Try requesting that brainstorm before you share your own thoughts on what to build.
- If the agent is too eager to switch from thought partnership to building, use question mode.
- After open discussion, switch to plan mode (
Shift + Tab). - Review the agent's plan carefully. Ask it to explain things you don't understand, or that strike you as questionable.
- Make big plans, so the agent can run independently for longer. Assign 10 tickets at a time, not 1.
- Your plan should usually include "comprehensively test using Chrome" and "do code review". Make sure the agent can use Chrome. To test a browser extension, use this skill.
- For web apps, use an agent-friendly framework like Convex.
- For planning, Codex 5.4 is as good or better than Opus 4.6. YMMV.
- For big projects, make a proper PRD. If you're doing this often, try ChatPRD.
- When planning, consider using fast mode (
/fast on). You'll save a bunch of time, and the cost may make you think harder.1 - For difficult projects, ask several models.
