Summary audio
Spoken summary — press play to read along: the line being spoken stays near the top.
Study notes
Core Workflow
- Explore → Plan → Code → Commit
- Avoid jumping straight to coding; this reduces course-correction later
Explore & Plan Phase
- Use Plan Mode (Shift+Tab) to explore without editing files
- Claude reads files, researches, and generates an action plan
- Review the plan before approval — this is the best place to course-correct before code is written
- Can also explore codebase without Plan Mode by asking Claude directly
Plan Approval & Execution
- Select Approve to accept the plan
- Choose whether Claude auto-accepts file edits or asks for confirmation each time
- Claude troubleshoots before marking the plan complete
Making Plans Effective
- Be explicit about what you consider "correct" in your plan
- Add tools to help Claude succeed:
- Use Claude in Chrome extension for UI testing
- Include a test suite Claude can validate against continuously
- Ensure tests are a source of truth for your team
Code Phase
- Collaborate with Claude through iterations until results match the plan
- Use context from the plan to guide course-corrections
Commit Phase
- Run a sub-agent code reviewer before committing
- Have Claude generate a commit message in your style
- Review and push code to start the next feature
Takeaways
- Plan before coding: Use Plan Mode to explore and generate an action plan, then review and approve it—this is the most effective place to catch issues before writing code.
- Be explicit about success criteria: Clearly define what "correct" means in your plan so Claude can validate work accurately throughout the workflow.
- Add validation tools: Include test suites, UI testing capabilities, and other tools that Claude can use continuously to verify work matches the plan.
- Iterate collaboratively: After approval, work through code iterations with Claude using the plan as a reference guide for course-corrections.
- Review before committing: Use a code reviewer sub-agent and have Claude generate commit messages before pushing to ensure quality control at the final step.
Flashcards 10 cards
Question
click to reveal · ←/→
Answer
click to flip back
Knowledge check 6 questions