deep-planning
Research and clarify complex software changes before implementation. Use for architecture proposals, migrations and refactors, parity or retirement inventories, sequencing and dependency analysis, scope and tradeoff decisions, ADR candidates, acceptance gates, and other software work that needs repository evidence plus targeted user questions. Do not use for straightforward changes with an already decision-complete specification.
Pinned to revision 680d339b0581, so it is the text this page describes rather than whatever the author pushed since.
Files
Every link opens the file at its source, pinned to the revision this page describes.