specswarm-modify

# 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 SpecS