Best for
- Turning impact findings into a tracked checklist
- Catching scope growth the moment it happens
- Change processes that need an audit trail
What you give it
- The impact-analysis result, and the change it belongs to
What you get back
- The impacted-elements inventory recorded in the change's spec
- Per-task rows updated to cover every element
- Drift reports when new impacts appear mid-build
How it works
- Takes the analysis output and the target specification.
- Writes the inventory in the spec's standard section.
- Cross-checks tasks against elements — every element needs an owner task.
- Appends later discoveries with dates rather than rewriting history.
- Reports uncovered elements as the actionable gap list.
Example
You: Record the impact findings for the tax-rate change into its spec.
Result: Eleven elements written into the spec's inventory, two new task rows added to cover elements no task owned, and one earlier-missed report page appended with a dated note.
Limits — please read
- It records analysis; producing the analysis is its own skill.
- An element without an owning task is flagged, not silently assigned.
- It tracks code-adjacent impact; organisational impact needs your judgement.