2.6 KiB
name, description, allowed-tools
| name | description | allowed-tools |
|---|---|---|
| specswarm-build | 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. | AskUserQuestion, SlashCommand |
SpecSwarm Build Workflow
Provides natural language access to /specswarm:build command.
When to Invoke
Trigger this skill when the user mentions:
- Building, creating, or adding features
- Implementing or developing functionality
- Making or adding components
- Any request to build software features
Examples:
- "Build user authentication"
- "Create a payment system"
- "Add dashboard analytics"
- "Implement shopping cart"
Instructions
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:
- Clear feature requests: "Please build a simple website", "Create user authentication with JWT", "Add dashboard analytics"
- Action: Immediately run
/specswarm:build "feature description" - Show brief notification: "🎯 Running /specswarm:build... (press Ctrl+C within 3s to cancel)"
Medium Confidence (70-94%) - Ask for confirmation:
- Less specific: "Add authentication", "Build a feature"
- Action: Use AskUserQuestion tool with two options:
- Option 1 (label: "Run /specswarm:build"): Use SpecSwarm's complete workflow
- Option 2 (label: "Process normally"): Handle as regular Claude Code request
Low Confidence (<70%) - Always ask:
- Vague: "Work on the app", "Improve the code"
- Action: Use AskUserQuestion as above
-
If user cancels (Ctrl+C) or selects Option 2, process normally without SpecSwarm
-
After command completes, STOP - do not continue with ship/merge
What the Build Command Does
/specswarm:build runs complete workflow:
- Creates specification
- Asks clarifying questions
- Generates implementation plan
- Breaks down into tasks
- Implements all tasks
- Validates quality
Stops after implementation - does NOT merge/ship/deploy.
Semantic Understanding
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
Example
User: "Build user authentication with JWT"