Initial commit
This commit is contained in:
Zhongwei Li
73
skills/specswarm-build/SKILL.md
Normal file
73
skills/specswarm-build/SKILL.md
Normal file
@@ -0,0 +1,73 @@
|
||||
---
|
||||
name: specswarm-build
|
||||
description: 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.
|
||||
allowed-tools: 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:**
|
||||
|
||||
1. **Detect** that user mentioned building/creating software
|
||||
2. **Extract** the feature description from their message
|
||||
3. **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
|
||||
|
||||
4. **If user cancels (Ctrl+C) or selects Option 2**, process normally without SpecSwarm
|
||||
5. **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"
|
||||
73
skills/specswarm-fix/SKILL.md
Normal file
73
skills/specswarm-fix/SKILL.md
Normal file
@@ -0,0 +1,73 @@
|
||||
---
|
||||
name: specswarm-fix
|
||||
description: Systematic bugfix workflow with regression testing, auto-retry logic, and comprehensive validation. Auto-executes when user clearly wants to fix, debug, repair, resolve, broken, not working, doesn't work, not showing up, not appearing, not displaying, not rendering, doesn't show, won't show, isn't showing, doesn't appear, doesn't display, failing, errors, bugs, issues, not loading, doesn't load, crashed, crashes, problem with, trouble with.
|
||||
allowed-tools: AskUserQuestion, SlashCommand
|
||||
---
|
||||
|
||||
# SpecSwarm Fix Workflow
|
||||
|
||||
Provides natural language access to `/specswarm:fix` command.
|
||||
|
||||
## When to Invoke
|
||||
|
||||
Trigger this skill when the user describes ANY software problem:
|
||||
- Things not working or broken
|
||||
- Errors, bugs, or failures
|
||||
- Features not loading or functioning
|
||||
- Requests to fix, debug, or resolve issues
|
||||
- ANY report of unexpected behavior
|
||||
|
||||
**Examples:**
|
||||
- "Please fix that the images don't load"
|
||||
- "Images don't load"
|
||||
- "Fix the login bug"
|
||||
- "The checkout is broken"
|
||||
- "There's an error when submitting forms"
|
||||
- "Authentication doesn't work"
|
||||
- "Payment processing fails"
|
||||
- "The search isn't working"
|
||||
|
||||
## Instructions
|
||||
|
||||
**Confidence-Based Execution:**
|
||||
|
||||
1. **Detect** that user described a software problem
|
||||
2. **Extract** the problem description from their message
|
||||
3. **Assess confidence and execute accordingly**:
|
||||
|
||||
**High Confidence (95%+)** - Auto-execute immediately:
|
||||
- Clear bug descriptions: "fix the login bug", "images don't load", "checkout is broken"
|
||||
- Action: Immediately run `/specswarm:fix "problem description"`
|
||||
- Show brief notification: "🎯 Running /specswarm:fix... (press Ctrl+C within 3s to cancel)"
|
||||
|
||||
**Medium Confidence (70-94%)** - Ask for confirmation:
|
||||
- Less specific: "something's wrong with authentication", "the app has issues"
|
||||
- Action: Use AskUserQuestion tool with two options:
|
||||
- Option 1 (label: "Run /specswarm:fix"): Use SpecSwarm's systematic bugfix workflow
|
||||
- Option 2 (label: "Process normally"): Handle as regular Claude Code request
|
||||
|
||||
**Low Confidence (<70%)** - Always ask:
|
||||
- Vague: "the app isn't working right", "there's a problem"
|
||||
- Action: Use AskUserQuestion as above
|
||||
|
||||
4. **If user cancels (Ctrl+C) or selects Option 2**, process normally without SpecSwarm
|
||||
5. **After command completes**, STOP - do not continue with ship/merge
|
||||
|
||||
## What the Fix Command Does
|
||||
|
||||
`/specswarm:fix` runs complete workflow:
|
||||
- Creates regression tests to reproduce bug
|
||||
- Implements the fix
|
||||
- Verifies fix works
|
||||
- Re-runs tests to catch new failures
|
||||
- Auto-retries up to 2 times if needed
|
||||
|
||||
Stops after bug is fixed - does NOT merge/ship/deploy.
|
||||
|
||||
## Semantic Understanding
|
||||
|
||||
This skill should trigger not just on exact keywords, but semantic equivalents:
|
||||
|
||||
**Fix equivalents**: fix, repair, resolve, debug, correct, address, handle, patch
|
||||
**Broken equivalents**: broken, not working, doesn't work, not showing, not appearing, not displaying, not rendering, not loading, failing, crashed
|
||||
**Issue terms**: bug, error, problem, issue, trouble, failure
|
||||
100
skills/specswarm-modify/SKILL.md
Normal file
100
skills/specswarm-modify/SKILL.md
Normal file
@@ -0,0 +1,100 @@
|
||||
---
|
||||
name: specswarm-modify
|
||||
description: Impact-analysis-first modification workflow with backward compatibility assessment and breaking change detection. Auto-executes when user clearly wants to modify, change, update, adjust, enhance, extend, or alter existing feature behavior (not fixing bugs, not refactoring quality). For features that work but need to work differently.
|
||||
allowed-tools: AskUserQuestion, SlashCommand
|
||||
---
|
||||
|
||||
# SpecSwarm Modify Workflow
|
||||
|
||||
Provides natural language access to `/specswarm:modify` command.
|
||||
|
||||
## When to Invoke
|
||||
|
||||
Trigger this skill when the user mentions:
|
||||
- Modifying, changing, or updating existing feature behavior
|
||||
- Enhancing or extending working features
|
||||
- Altering how something works (that currently works)
|
||||
- Making features work differently than they do now
|
||||
|
||||
**Examples:**
|
||||
- "Change authentication from session to JWT"
|
||||
- "Add pagination to the user list API"
|
||||
- "Update search to use full-text search"
|
||||
- "Modify the dashboard to show real-time data"
|
||||
- "Extend the API to support filtering"
|
||||
|
||||
**NOT for this skill:**
|
||||
- Fixing bugs (use specswarm-fix)
|
||||
- Improving code quality without changing behavior (use specswarm-refactor)
|
||||
- Building new features (use specswarm-build)
|
||||
|
||||
## Instructions
|
||||
|
||||
**Confidence-Based Execution:**
|
||||
|
||||
1. **Detect** that user mentioned modifying/changing existing functionality
|
||||
2. **Extract** the modification description from their message
|
||||
3. **Assess confidence and execute accordingly**:
|
||||
|
||||
**High Confidence (95%+)** - Auto-execute immediately:
|
||||
- Clear modification requests: "Change authentication from session to JWT", "Add pagination to user list API", "Update search algorithm to use full-text search"
|
||||
- Action: Immediately run `/specswarm:modify "modification description"`
|
||||
- Show brief notification: "🎯 Running /specswarm:modify... (press Ctrl+C within 3s to cancel)"
|
||||
|
||||
**Medium Confidence (70-94%)** - Ask for confirmation:
|
||||
- Less specific: "Update the authentication", "Modify the search"
|
||||
- Action: Use AskUserQuestion tool with two options:
|
||||
- Option 1 (label: "Run /specswarm:modify"): Use SpecSwarm's impact-analysis workflow
|
||||
- Option 2 (label: "Process normally"): Handle as regular Claude Code request
|
||||
|
||||
**Low Confidence (<70%)** - Always ask:
|
||||
- Vague: "Make the feature better", "Improve the UI"
|
||||
- Action: Use AskUserQuestion as above
|
||||
|
||||
4. **If user cancels (Ctrl+C) or selects Option 2**, process normally without SpecSwarm
|
||||
5. **After command completes**, STOP - do not continue with ship/merge
|
||||
|
||||
## What the Modify Command Does
|
||||
|
||||
`/specswarm:modify` runs complete workflow:
|
||||
- Analyzes impact and backward compatibility
|
||||
- Identifies breaking changes
|
||||
- Creates migration plan if needed
|
||||
- Updates specification and plan
|
||||
- Generates modification tasks
|
||||
- Implements changes
|
||||
- Validates against regression tests
|
||||
|
||||
Stops after modification is complete - does NOT merge/ship/deploy.
|
||||
|
||||
## Semantic Understanding
|
||||
|
||||
This skill should trigger not just on exact keywords, but semantic equivalents:
|
||||
|
||||
**Modify equivalents**: modify, change, update, adjust, enhance, extend, alter, revise, adapt, transform, convert
|
||||
**Target terms**: feature, functionality, behavior, workflow, process, mechanism, system
|
||||
|
||||
**Distinguish from:**
|
||||
- **Fix** (broken/not working things): "fix", "repair", "resolve", "debug"
|
||||
- **Refactor** (code quality): "refactor", "clean up", "reorganize", "optimize code structure"
|
||||
- **Build** (new things): "build", "create", "add", "implement new"
|
||||
|
||||
## Example
|
||||
|
||||
```
|
||||
User: "Change authentication from session to JWT"
|
||||
|
||||
Claude: 🎯 Running /specswarm:modify... (press Ctrl+C within 3s to cancel)
|
||||
|
||||
[Executes /specswarm:modify "Change authentication from session to JWT"]
|
||||
```
|
||||
|
||||
```
|
||||
User: "Update the authentication"
|
||||
|
||||
Claude: [Shows AskUserQuestion]
|
||||
1. Run /specswarm:modify - Use SpecSwarm's impact-analysis workflow
|
||||
2. Process normally - Handle as regular Claude Code request
|
||||
|
||||
User selects Option 1
|
||||
```
|
||||
74
skills/specswarm-ship/SKILL.md
Normal file
74
skills/specswarm-ship/SKILL.md
Normal file
@@ -0,0 +1,74 @@
|
||||
---
|
||||
name: specswarm-ship
|
||||
description: 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).
|
||||
allowed-tools: AskUserQuestion, SlashCommand
|
||||
---
|
||||
|
||||
# SpecSwarm Ship Workflow
|
||||
|
||||
Provides natural language access to `/specswarm:ship` command.
|
||||
|
||||
## When to Invoke
|
||||
|
||||
Trigger this skill when the user mentions:
|
||||
- Shipping, deploying, or releasing features
|
||||
- Merging to main/production
|
||||
- Completing or finishing features
|
||||
- "Ship it" (common casual phrase - ALWAYS confirm)
|
||||
|
||||
**Examples:**
|
||||
- "Ship the authentication feature"
|
||||
- "Deploy to production"
|
||||
- "Merge this to main"
|
||||
- "Ship it" ← Ambiguous - might be casual approval
|
||||
- "Release version 2.0"
|
||||
|
||||
## Instructions
|
||||
|
||||
**ALWAYS Confirm (Regardless of Confidence):**
|
||||
|
||||
1. **Detect** that user mentioned shipping/deploying/merging
|
||||
2. **Extract** context about what to ship (if provided)
|
||||
3. **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**:
|
||||
- **Option 1** (label: "Yes, ship this feature"): "Merge to main branch and delete feature branch (DESTRUCTIVE)"
|
||||
- **Option 2** (label: "No, cancel"): "Cancel - I'm not ready to ship" (or if this was just casual "ship it" approval)
|
||||
|
||||
4. **If user selects Option 1**, run: `/specswarm:ship`
|
||||
5. **If user selects Option 2**, process normally without SpecSwarm
|
||||
6. **Note**: The `/specswarm:ship` command may have its own confirmation as an additional safety layer
|
||||
|
||||
## What the Ship Command Does
|
||||
|
||||
`/specswarm:ship` runs complete workflow:
|
||||
- Runs quality analysis and validation
|
||||
- Checks quality threshold (default 80%)
|
||||
- **Shows merge plan with confirmation prompt**
|
||||
- Merges to parent branch
|
||||
- Cleans up feature branch
|
||||
|
||||
**Important:** This is DESTRUCTIVE - it merges and deletes branches. The command itself may have built-in confirmation as a second safety layer.
|
||||
|
||||
## Semantic Understanding
|
||||
|
||||
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
|
||||
|
||||
## Example
|
||||
|
||||
```
|
||||
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)
|
||||
```
|
||||
74
skills/specswarm-upgrade/SKILL.md
Normal file
74
skills/specswarm-upgrade/SKILL.md
Normal file
@@ -0,0 +1,74 @@
|
||||
---
|
||||
name: specswarm-upgrade
|
||||
description: 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.
|
||||
allowed-tools: AskUserQuestion, SlashCommand
|
||||
---
|
||||
|
||||
# SpecSwarm Upgrade Workflow
|
||||
|
||||
Provides natural language access to `/specswarm:upgrade` command.
|
||||
|
||||
## When to Invoke
|
||||
|
||||
Trigger this skill when the user mentions:
|
||||
- Upgrading or updating dependencies/packages
|
||||
- Migrating to new frameworks or versions
|
||||
- Modernizing technology stacks
|
||||
- Bumping version numbers
|
||||
|
||||
**Examples:**
|
||||
- "Upgrade React to version 19"
|
||||
- "Update all dependencies"
|
||||
- "Migrate from Webpack to Vite"
|
||||
- "Modernize the build system"
|
||||
- "Bump Node to version 20"
|
||||
|
||||
## Instructions
|
||||
|
||||
**Confidence-Based Execution:**
|
||||
|
||||
1. **Detect** that user mentioned upgrading/updating software
|
||||
2. **Extract** what to upgrade from their message
|
||||
3. **Assess confidence and execute accordingly**:
|
||||
|
||||
**High Confidence (95%+)** - Auto-execute immediately:
|
||||
- Clear upgrade requests: "Upgrade React to version 19", "Update all dependencies", "Migrate from Webpack to Vite"
|
||||
- Action: Immediately run `/specswarm:upgrade "upgrade description"`
|
||||
- Show brief notification: "🎯 Running /specswarm:upgrade... (press Ctrl+C within 3s to cancel)"
|
||||
|
||||
**Medium Confidence (70-94%)** - Ask for confirmation:
|
||||
- Less specific: "Update the packages", "Modernize the stack"
|
||||
- Action: Use AskUserQuestion tool with two options:
|
||||
- Option 1 (label: "Run /specswarm:upgrade"): Use SpecSwarm's upgrade workflow with compatibility analysis
|
||||
- Option 2 (label: "Process normally"): Handle as regular Claude Code request
|
||||
|
||||
**Low Confidence (<70%)** - Always ask:
|
||||
- Vague: "Make it better", "Use newer stuff"
|
||||
- Action: Use AskUserQuestion as above
|
||||
|
||||
4. **If user cancels (Ctrl+C) or selects Option 2**, process normally without SpecSwarm
|
||||
5. **After command completes**, STOP - do not continue with ship/merge
|
||||
|
||||
## What the Upgrade Command Does
|
||||
|
||||
`/specswarm:upgrade` runs complete workflow:
|
||||
- Analyzes breaking changes and compatibility
|
||||
- Creates comprehensive upgrade plan
|
||||
- Generates migration tasks
|
||||
- Updates dependencies and code
|
||||
- Runs tests to verify compatibility
|
||||
- Documents upgrade process
|
||||
|
||||
Stops after upgrade is complete - does NOT merge/ship/deploy.
|
||||
|
||||
## Semantic Understanding
|
||||
|
||||
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
|
||||
|
||||
## Example
|
||||
|
||||
```
|
||||
User: "Upgrade React to version 19"
|
||||
Reference in New Issue
Block a user