Planning mode protects discovery before edits
A planning session should map the relevant flow, identify constraints, and turn findings into a small implementation plan. It is valuable when the repository or failure path is unfamiliar.
The planning output should name evidence and open questions rather than pretending that a hypothesis is settled.
| Planning output | Review question |
|---|---|
| Entry point | Where does the behavior begin? |
| Flow | Which modules and boundaries are involved? |
| Risk | What could the change affect? |
| Checks | What can verify the result? |
| Open questions | What still needs confirmation? |
Discovery sequence
- Inspect repository instructions and status.
- Find the entry point and trace the relevant flow.
- Read neighboring tests and configuration.
- Record affected files with file:line evidence.
- Separate facts, hypotheses, and missing data.
- Propose one bounded implementation slice.
Planning note
# Plan discovery
Question: <behavior>
Entry point: <path:line>
Flow: <modules>
Constraints: <list>
Evidence: <files and checks>
Unknowns: <list>
Next: <smallest change>Canonical lesson source · JavaRush
Open JavaRush material