Systematic compatibility analysis, migration guidance, and breaking change detection for dependency/framework upgrades. Auto-executes when user clearly wants to upgrade, update, migrate, or modernize software dependencies, frameworks, packages, or technology stacks.
/plugin marketplace add MartyBonacci/specswarm/plugin install specswarm@specswarmThis skill is limited to using the following tools:
Provides natural language access to /specswarm:upgrade command.
Trigger this skill when the user mentions:
Examples:
Confidence-Based Execution:
Detect that user mentioned upgrading/updating software
Extract what to upgrade from their message
Assess confidence and execute accordingly:
High Confidence (95%+) - Auto-execute immediately:
/specswarm:upgrade "upgrade description"Medium Confidence (70-94%) - Ask for confirmation:
Low Confidence (<70%) - Always ask:
If user cancels (Ctrl+C) or selects Option 2, process normally without SpecSwarm
After command completes, STOP - do not continue with ship/merge
/specswarm:upgrade runs complete workflow:
Stops after upgrade is complete - does NOT merge/ship/deploy.
This skill should trigger not just on exact keywords, but semantic equivalents:
Upgrade equivalents: upgrade, update, migrate, modernize, bump, move to, switch to, adopt Target terms: dependency, package, framework, library, version, technology stack
User: "Upgrade React to version 19"
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.