tmr-project-impact

tmr-project-impact

Detects changes in declared source-of-truth files within a project and produces a human-readable impact report with per-document suggestions. Nothing is applied automatically — you review and decide.

Usage

• /tmr-project-impact — run against the project in the current working directory
• /tmr-project-impact <project-path> — run against a specific project (path relative to vault root)
• /tmr-project-impact deps — interactively create deps.yaml for the current project
• /tmr-project-impact <project-path> deps — interactively create deps.yaml for a specific project

The vault root is the git repository root. All relative paths in this skill are relative to the vault root unless stated otherwise.

---

EXECUTION

When invoked, check if the user passed the argument deps (in any position). If so, follow the CREATE-DEPS section. Otherwise, follow these steps in order: LOCATE, DETECT, ANALYZE, REPORT.

---

LOCATE

Step L1: Resolve the project path

If a <project-path> argument was given, use it as the project root (relative to vault root).

If no argument was given:

1. Run git rev-parse --show-toplevel to get the vault root
2. Run pwd to get the current working directory
3. Compute the relative path from vault root to cwd — this is the project path
4. If the relative path is . or empty (you are at the vault root), ask:

   No project path provided and you are at the vault root.
   Which project? (e.g., my-company/projects/ai-enablement):
   

   Wait for the user's response and use it as the project path.

Store as PROJECT_ROOT = <vault-root>/<project-path>.

Step L2: Find and load deps.yaml

Check if <PROJECT_ROOT>/deps.yaml exists.

If it does NOT exist: Print:

No deps.yaml found in <project-path>.

Options:
  a) Create deps.yaml interactively → /tmr-project-impact <project-path> deps
  b) Cancel

Wait for the user's response. If a, follow the CREATE-DEPS section. If b or anything else, exit.