Systematic quality validation, test verification, and safe merging workflow for deployment/release operations. ALWAYS asks for confirmation when user wants to ship, deploy, merge, release, or complete features to production, merge to main branch, or finalize features. This is a DESTRUCTIVE operation (merges and deletes branches).
/plugin marketplace add MartyBonacci/specswarm/plugin install specswarm@specswarmThis skill is limited to using the following tools:
Provides natural language access to /specswarm:ship command.
Trigger this skill when the user mentions:
Examples:
ALWAYS Confirm (Regardless of Confidence):
Detect that user mentioned shipping/deploying/merging
Extract context about what to ship (if provided)
ALWAYS ask for confirmation using AskUserQuestion tool with this format:
Question: "⚠️ SHIP CONFIRMATION - Destructive Operation"
Description: "This will merge your feature branch to main/parent branch and delete the feature branch. This is a DESTRUCTIVE operation that cannot be easily undone."
Options:
If user selects Option 1, run: /specswarm:ship
If user selects Option 2, process normally without SpecSwarm
Note: The /specswarm:ship command may have its own confirmation as an additional safety layer
/specswarm:ship runs complete workflow:
Important: This is DESTRUCTIVE - it merges and deletes branches. The command itself may have built-in confirmation as a second safety layer.
This skill should trigger not just on exact keywords, but semantic equivalents:
Ship equivalents: ship, deploy, release, merge, publish, finalize, complete, deliver Target terms: production, main, master, parent branch, live, release
User: "Ship it"
Claude: [Shows AskUserQuestion]
1. Run /specswarm:ship - ⚠️ Merge feature to parent branch (DESTRUCTIVE)
2. Process normally - Handle as regular request
User selects Option 2 (it was casual approval, not actual shipping request)
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.