If the user's intent does not match this skill, activate /plugin-creator:plugin-lifecycle to route it.

Plan Plugin Refactoring

<plugin_name> $ARGUMENTS </plugin_name>

Execute the phases in order. Before Phase 1, create separate tracking tasks named for assessment, design, task-file creation, plan-index update, context gathering, and final handoff. Mark each in progress before execution and complete only after verifying its output. After each phase, display its key findings and output paths before continuing.

Phase 1: Assess

Dispatch plugin-creator:plugin-assessor with:

• Input: ./plugins/<plugin_name>/ and the request to assess structural correctness, quality issues, and refactoring opportunities.
• Context: identify the plugin manifest and any skill, command, agent, hook, MCP, and reference content under the plugin root.
• Execution ownership: the agent runs its complete assessment protocol. Do not restate its phases, schemas, or scoring rules in the dispatch prompt.
• Required output: the standard assessment produced through its preloaded /plugin-creator:assessment-reporting skill, including marketplace readiness, scored findings, affected paths, severities, orphan classifications, and recommended execution roles.
• Completion: STATUS: DONE plus the inline report or report path. STATUS: BLOCKED must name the missing input.