Claude Code Practical Workflows – CLI, Planning, Worktrees, and Automation
Lesson 3: Planning, Refactoring, and Documentation Work
Lesson Objectives
By the end of this lesson, students should be able to:
- Use plan-first prompting for risky changes.
- Split refactors into small testable steps.
- Ask for documentation that explains behavior, not filler.
Lesson Content
Plan-first work is useful when the edit is risky, broad, or expensive to undo. Ask Claude Code to inspect, propose options, name risks, and wait. Once the plan is acceptable, approve a narrow implementation.
Refactors should preserve behavior. Documentation should explain decisions, user-facing behavior, setup, and troubleshooting. A polished paragraph that repeats the function name is not useful documentation.
Enroll to continue this lesson.
The preview above shows the lesson objectives and opening lesson content. Enroll to view the full lesson, complete the practice work, and take the lesson quiz.