Systematic spec-driven workflow (specification→clarification→planning→tasks→implementation→validation) for feature development. Auto-executes when user clearly wants to build, create, add, implement, develop, make, construct, or set up software features, components, or functionality.
/plugin marketplace add MartyBonacci/specswarm/plugin install specswarm@specswarmThis skill is limited to using the following tools:
Provides natural language access to /specswarm:build command.
Trigger this skill when the user mentions:
Examples:
Confidence-Based Execution:
Detect that user mentioned building/creating software
Extract the feature description from their message
Assess confidence and execute accordingly:
High Confidence (95%+) - Auto-execute immediately:
/specswarm:build "feature 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:build runs complete workflow:
Stops after implementation - does NOT merge/ship/deploy.
This skill should trigger not just on exact keywords, but semantic equivalents:
Build equivalents: build, create, make, develop, implement, add, construct, set up, establish, design Feature terms: feature, component, functionality, module, system, page, form, interface
User: "Build user authentication with JWT"
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.