The Explore → Plan → Code → Commit workflow in Claude Code — Transcript

Full transcript

1. 0:03If you take one thing away from Claude
2. 0:05code, let it be this workflow: explore,
3. 0:08plan, code, and commit.
4. 0:13Without this, most people jump straight
5. 0:15to pasting in Claude to write code,
6. 0:17which means more course correcting later
7. 0:18on.
8. 0:21The fastest way to handle step one and
9. 0:23two is with plan mode. With plan mode,
10. 0:25Claude can't edit files. It just reads
11. 0:27files to gather research on how to
12. 0:29tackle this implementation. To enter
13. 0:31plan mode, hit shift and tab until you
14. 0:33see the plan mode under the text input.
15. 0:36I need to add WebP conversion to our
16. 0:38image upload pipeline. Figure out where
17. 0:40in the pipeline it should happen,
18. 0:41whether we need new dependencies, and
19. 0:43how to approach it.
20. 0:44And Claude will read relevant files, do
21. 0:47some web searches, and give you a plan
22. 0:49of action.
23. 0:50Make sure you review it and determine if
24. 0:52it meets your criteria.
25. 0:54Otherwise, I can ask it to add on or
26. 0:57revise some areas.
27. 0:59Perfect. And this right here is the best
28. 1:02place to course correct because it's
29. 1:03before any code is written. You can also
30. 1:06use explore without being in plan mode
31. 1:07by just asking Claude to explore your
32. 1:09code base.
33. 1:11Now, once the plan looks good, you can
34. 1:14select approve to accept the plan and
35. 1:16let Claude toggle all of the list items
36. 1:18it provided. You can determine if you
37. 1:19want Claude to auto accept the file
38. 1:21edits or ask every single time. Claude
39. 1:23will do its best to troubleshoot your
40. 1:24code base before considering the plan
41. 1:26finished. But at times, you'll need to
42. 1:29course correct. This is the benefit of
43. 1:31working with plan mode because after the
44. 1:32plan is finished, we also have the
45. 1:34context of how it got to the results to
46. 1:36help it guide its next decision.
47. 1:39In order for Claude to be confident in
48. 1:40its results, it has to be clear on what
49. 1:43it deems correct. When writing your
50. 1:45plan, make this explicit.
51. 1:49Adding tools that will help Claude
52. 1:50complete its goals will remove a lot of
53. 1:52back and forth.
54. 1:54For example, if you're building web UIs,
55. 1:56make sure you have the Claude and Chrome
56. 1:58extension so that Claude code can
57. 1:59control a tab and test out the UI before
58. 2:02deeming it finished.
59. 2:04In your project, include a test suite
60. 2:05that Claude can continuously validate
61. 2:07on.
62. 2:08Claude can even write tests for you.
63. 2:10Before passing this off to Claude, make
64. 2:12sure that the tests are a source of
65. 2:14truth for you and your team to avoid any
66. 2:16false positives.
67. 2:17Quick tip, if you find Claude keeps
68. 2:19running into the same issues, ask Claude
69. 2:21to save the solution to his Claude MD
70. 2:23file.
71. 2:25Now, once you have tested for yourself
72. 2:27and are happy with the results, it's
73. 2:28time to push your code. A tip before you
74. 2:30commit, run a sub agent code reviewer to
75. 2:33look at your code.
76. 2:34Then you get Claude to generate a commit
77. 2:36message for you in your style. Rinse and
78. 2:38repeat.
79. 2:39>> [music]
80. 2:43>> If you want to be effective with Claude
81. 2:45code, follow the explore, plan, code,
82. 2:47and commit workflow. Exploration will
83. 2:49give the relevant context Claude needs
84. 2:51for your project. Plan will create a
85. 2:53plan of action that Claude will use to
86. 2:55determine if they are successful. Code
87. 2:57is the back and forth that you and
88. 2:58Claude do before settling on the final
89. 3:00outcomes of the plan.
90. 3:02Commit helps you review and push your
91. 3:04code so you can start on your next
92. 3:05feature.