Issue-to-PR begins with an intake boundary
An issue is a request or signal, not yet an implementation plan. Convert it into a bounded goal, current behavior, desired behavior, scope, non-goals, acceptance, and verification before editing.
Keep external wording separate from facts confirmed in the repository.
| Stage | Output |
|---|---|
| Intake | Issue Intake Note |
| Discovery | Affected files and behavior evidence |
| Planning | TASK_SPEC.md and PLAN.md |
| Implementation | Small diff |
| Review | Checks, findings, and decision |
Issue-to-PR sequence
- Read the issue and identify missing information.
- Inspect the repository and confirm the affected area.
- Write the task boundary and stop conditions.
- Agree on a plan before editing.
- Implement one reviewable slice.
- Run focused checks and inspect the diff.
- Prepare a reviewer-ready handoff.
Intake record
# Issue Intake Note
Signal: <issue text>
Confirmed behavior: <facts>
Unknowns: <questions>
Candidate area: <paths>
Next check: <command or file>
Status: documented example.Canonical lesson source · JavaRush
Open JavaRush material