Best for
- Sizing a change honestly before you promise a date
- Finding the tests and copy that will break
- Catching a risky data-model change early
What you give it
- The requirement in the person's own words
- Your open changes, so overlaps are visible
What you get back
- A list per layer: element, why it is affected, edit/new/remove/test/doc, risk
- A flag on anything that needs approval
- Open questions with a recommended answer
How it works
- Lists the words people use for the feature, including old names.
- Searches every layer for each word instead of assuming.
- Cross-checks decisions and other open changes.
- Writes the structured list and hands it on. Never edits files.
Example
You: /impact-analysis rename "Membership" to "Plan"
Result: Routes: /membership → /plan (redirect). UI: nav, 6 components. Emails: 3 templates. Tests: 9 specs assert the old word. Docs: terms page. DB: none. Risk: SEO — keep a permanent redirect.
Limits — please read
- Search finds text, not intent: skim the results.
- It does not estimate effort.