---
name: Plugin Impact Review
slug: plugin-impact-review
category: Automation
description: Plugin Impact Review assesses which skills, hooks, and docs need updates after MCP, config, or output-shape changes. Use it when filling plugin-impact notes and checking cached hook or skill references.
github: "https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/plugin-impact-review"
language: Kotlin
stars: 206
forks: 20
install: "npx degit https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/plugin-impact-review ~/.claude/skills/plugin-impact-review"
installs_to: ~/.claude/skills/plugin-impact-review
source_path: .claude/skills/plugin-impact-review/SKILL.md
collection_size: 25
category_size: 1956
collection_url: "https://dirskills.com/collections/jpicklyk/task-orchestrator"
added: 2026-09-05T05:28:55.044Z
last_synced: 2026-09-05T05:28:55.044Z
canonical_url: "https://dirskills.com/skills/plugin-impact-review"
---

# Plugin Impact Review

Plugin Impact Review assesses which skills, hooks, and docs need updates after MCP, config, or output-shape changes. Use it when filling plugin-impact notes and checking cached hook or skill references.

**Install:**

```bash
npx degit https://github.com/jpicklyk/task-orchestrator/tree/main/.claude/skills/plugin-impact-review ~/.claude/skills/plugin-impact-review
```

## README

# Plugin Impact Review Framework

Evaluate which plugin components need updating after changes to MCP tools, config format, or response shapes.

## Step 1: Skill Impact

Search all skill files for references to the changed behavior:

```
grep -r "<tool-name>\|<config-key>\|<changed-concept>" claude-plugins/task-orchestrator/skills/
```

For each match:
- [ ] Does the skill reference the old behavior, field name, or response shape?
- [ ] Does the skill need updated instructions or examples?
- [ ] Are trigger phrases still accurate?

## Step 2: Hook Impact

Search hook scripts for references:

```
grep -r "<tool-name>\|<changed-concept>" claude-plugins/task-orchestrator/hooks/
```

For each match:
- [ ] Does the hook inject context that references the old behavior?
- [ ] Does the hook read tool input/output fields that changed?
- [ ] Does the hook matcher still target the correct tool name?

## Step 3: Config Format Documentation

Check `claude-plugins/task-orchestrator/skills/manage-schemas/references/config-format.md`:
- [ ] YAML structure example reflects current format
- [ ] Field reference table has all current fields
- [ ] Descriptions match current behavior

## Step 4: Output Style References

Check output styles for stale references:
- [ ] `workflow-orchestrator.md` — any references to changed tools, fields, or workflows
- [ ] Zone 1 (shared core) vs Zone 2/3 (extensions) — changes in Zone 1 must be synced to `workflow-analyst.md`

## Step 5: Plugin Caching

- [ ] Are hook scripts changed? If yes, `/plugin marketplace remove` + re-add required (content cached)
- [ ] Are skill files changed? `/reload-plugins` sufficient (read at invocation)
- [ ] Are output styles changed? `/reload-plugins` sufficient

## Output

Compose the `plugin-impact` note listing specific files and sections that need changes. Note `/mcp reconnect` requirements.

Before asserting any skill/hook/doc file is missing, verify with a direct existence check
(Read the exact expected path, or an exact-path Glob) — skills live in BOTH
`claude-plugins/task-orchestrator/skills/` and project-level `.claude/skills/`; checking
only one directory has produced a false "missing skill" finding before.