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: Orchestration Context References

Check the orchestration context for stale references:

• hooks/orchestration-context.mjs — any references to changed tools, fields, or workflows in the injected core (both the workflow and schema variants)
• skills/orchestrate/SKILL.md — tier table, delegation table, and phase-owner dispatch rules

Step 5: Generated Artifacts and Contracts

• Regenerate call shapes: node claude-plugins/task-orchestrator/scripts/gen-call-shapes.mjs (CI runs it with --check)
• Re-render the ralph prompts and the tier-classification fragments: node claude-plugins/task-orchestrator/scripts/render-ralph-prompts.mjs --check and node claude-plugins/task-orchestrator/_fragments/generate.mjs (TierClassificationConsistencyTest fails on drift)
• Contract tests pass: claude-plugins/task-orchestrator/hooks/tests/contract-*.test.mjs, and the to-call blocks in skills still match the tool shapes
• Other plugin consumers of the changed behavior: agents/*.md, workflows/, bundled-rules/, .taskorchestrator/rules/

Step 6: Plugin Caching

• Is any plugin file changed (skills, hooks, workflows, agents)? The cache is version-keyed and re-extracts lazily, so a plain marketplace update does not pick it up: run the forced refresh in claude-plugins/CLAUDE.md (rm -rf the cache, then marketplace update)
• Is the orchestration-context hook content changed? It also needs a session restart; the orchestrate skill is read at invocation

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.