Patch Scope Control
When a coding task is broad, keep each patch small enough to review and revert independently.
Steps
- List the files that must change for the behavior.
- Leave unrelated cleanup out of the patch.
- Commit after tests prove the slice works.
Provenance
Seeded during v1 starter-pack expansion from goal.md. Inspired by: https://github.com/obra/superpowers and https://github.com/garrytan/gstack.