planning-change-inventory

name	planning-change-inventory
description	Enumerate concrete files/components and intended edits tied to AC; not broad cross-system impact analysis

Make the plan executable: capture concrete edit points and the order Goal/requirements + impact areas Architecture/stack constraints Make a list of artifacts (files/modules/configs/migrations) For each, state: what changes and why (tie to AC/bug) Mark dependencies and order (what must happen first) Mark high-risk changes (for additional verification)

<output_format>

Artifacts list

Changes per artifact

Dependencies / order

<quality_rules> The list is finite and specific (not "change a couple of files") Every change is tied to the goal or AC </quality_rules>