Solo developer

Ship a feature without babysitting every edit

“I want the AI to change real code, but not to surprise me with what it changed.”

Plan first, fan the work out across isolated worktrees, review every diff in one place, and let the pull request wait for your approval rather than your attention.

1. 1

   Ask in Plan mode first

   Plan mode explores your repository read-only and writes one implementation plan. Nothing is edited until you approve it, and the plan stays browsable afterwards.

   Try this

   Copy

   Plan mode. I want to <what you want built> in this repository. Explore first, then write me one plan with the files you would touch and the order you would do them in. Change nothing yet.

   Plan Mode & Saved Plans→

   

2. 2

   Approve it and the same conversation starts working

   Approving switches the session to Code mode with the plan checklist already loaded, so nothing has to be re-explained.

   AI Chat & Modes→

   1:00

3. 3

   Fan the independent parts out

   One prompt across several agents, each in its own git worktree. They cannot collide because they are not in the same working copy.

   Try this

   Copy

   Fan the independent parts of this plan across 3 agents, one worktree each. Tell me which parts you judged independent and which you kept together.

   Parallel Agents Workspace→

   

4. 4

   Review the diffs in one panel

   Every tile that finished waits in one place across sessions. Merge with fast-forward, squash or cherry-pick, or discard it.

   Diff Review Queue→
5. 5

   Point at what looks wrong

   Dock the browser beside the chat, click the element on your dev server, and the selector, computed styles and a cropped screenshot land in the prompt.

   Try this

   Copy

   Look at the element I just picked in the browser pane. It breaks below 400px wide. Find the rule that causes it, fix it, and tell me what else that rule affects.

   Embedded Browser→

   

6. 6

   Run the tests yourself

   Start a message with ! and it runs in the session directory. The output becomes a terminal card and rides into context on your next message.

   Try this

   Copy

   !npm test

   Shell Commands→
7. 7

   Let the pull request review itself, and wait

   Every new issue gets a drafted reply and every pull request a verdict. Both sit in the Approvals panel until you press Post.

   Try this

   Copy

   Watch this repository from today onward. Draft a reply to every new issue and a review with a verdict on every new pull request, and hold both in Approvals until I post them.

   GitHub Auto-Review→