ss-modify
Modify features with impact analysis and compatibility checks. Triggers on modify/change/update/refactor intent.
What this skill does
# SpecSwarm Modify Workflow
Provides natural language access to `/ss: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
- Refactoring code for quality improvement (without changing behavior)
- Deprecating or sunsetting features
**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"
- "Refactor this module to reduce complexity" → uses `--refactor`
- "Deprecate the v1 API" → uses `--deprecate`
- "What's the impact of changing the user model?" → uses `--analyze-only`
**NOT for this skill:**
- Fixing bugs (use ss-fix)
- Building new features (use ss-build)
## Instructions
**Skill-Based Routing:**
1. **Detect** that user mentioned modifying/changing existing functionality
2. **Extract** the modification description from their message
3. **Route based on intent clarity**:
**Clear intent** - Execute directly:
- Clear modification requests: "Change authentication from session to JWT", "Add pagination to user list API", "Update search algorithm to use full-text search"
- Clear refactor requests: "Refactor this module to reduce complexity", "Clean up the utils to reduce duplication"
- Clear deprecation requests: "Deprecate the v1 API", "Sunset the legacy auth system"
- Action: Immediately run the appropriate command:
- Standard modify: `/ss:modify "modification description"`
- Refactor: `/ss:modify "target" --refactor`
- Deprecate: `/ss:modify "target" --deprecate`
- Impact analysis only: `/ss:modify "target" --analyze-only`
**Ambiguous intent** - Ask for confirmation:
- Less specific: "Update the authentication", "Make the feature better"
- Action: Use AskUserQuestion tool with two options:
- Option 1 (label: "Run /ss:modify"): Use SpecSwarm's workflow
- Option 2 (label: "Process normally"): Handle as regular Claude Code request
4. **If user selects Option 2**, process normally without SpecSwarm
5. **After command completes**, STOP - do not continue with ship/merge
## What the Modify Command Does
`/ss: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
**Refactor equivalents**: refactor, clean up, reorganize, simplify, reduce complexity, eliminate duplication, improve naming, optimize structure
**Deprecate equivalents**: deprecate, sunset, retire, phase out, remove feature, end-of-life
**Impact analysis equivalents**: what's the impact, analyze impact, dependency analysis, blast radius
**Target terms**: feature, functionality, behavior, workflow, process, mechanism, system, module, component
**Distinguish from:**
- **Fix** (broken/not working things): "fix", "repair", "resolve", "debug"
- **Build** (new things): "build", "create", "add", "implement new"
## Example
```
User: "Change authentication from session to JWT"
Claude: 🎯 Running /ss:modify... (press Ctrl+C within 3s to cancel)
[Executes /ss:modify "Change authentication from session to JWT"]
```
```
User: "Refactor the utils module to reduce complexity"
Claude: 🎯 Running /ss:modify --refactor... (press Ctrl+C within 3s to cancel)
[Executes /ss:modify "utils module" --refactor]
```
```
User: "Deprecate the v1 API"
Claude: 🎯 Running /ss:modify --deprecate... (press Ctrl+C within 3s to cancel)
[Executes /ss:modify "v1 API" --deprecate]
```
```
User: "What would be the impact of changing the user model?"
Claude: 🎯 Running /ss:modify --analyze-only...
[Executes /ss:modify "user model" --analyze-only]
```
```
User: "Update the authentication"
Claude: [Shows AskUserQuestion]
1. Run /ss:modify - Use SpecSwarm's workflow
2. Process normally - Handle as regular Claude Code request
User selects Option 1
```
Related in Code Review
gstack
IncludedFast headless browser for QA testing and site dogfooding. Navigate pages, interact with elements, verify state, diff before/after, take annotated screenshots, test responsive layouts, forms, uploads, dialogs, and capture bug evidence. Use when asked to open or test a site, verify a deployment, dogfood a user flow, or file a bug with screenshots. (gstack)
startup-due-diligence
IncludedLegal due diligence review for seed-stage and Series A startups (US, Delaware C-Corp focus). Supports both investor and founder perspectives. Capabilities include: (1) Interactive document review and issue spotting; (2) Document request list generation; (3) Cap table and SAFE/convertible note analysis; (4) Red flag identification with severity ratings; (5) Diligence report generation. TRIGGERS: due diligence, DD, startup investment, cap table review, Series A, seed round, investor diligence, legal review startup, SAFE analysis, convertible note, 409A, founder vesting.
interview-master
IncludedThis skill should be used when the user asks to "generate interview questions", "prepare for interview", "optimize resume", "conduct mock interview", "analyze git commits for resume", "generate resume from code", "review my resume", or mentions interview preparation, career assistance, or extracting project experience from git history. Provides comprehensive interview and career development guidance for both job seekers and interviewers.
fix-issue
IncludedFixes GitHub issues using parallel analysis agents for root cause investigation, code exploration, and regression detection. Reads issue context from gh CLI, searches codebase and memory for related patterns, generates a fix with tests, and links the resolution back to the issue via PR. Includes prevention analysis to avoid recurrence. Use when debugging errors, resolving regressions, fixing bugs, or triaging issues.
sf-apex
IncludedGenerates and reviews Salesforce Apex code with 150-point scoring. TRIGGER when: user writes, reviews, or fixes Apex classes, triggers, test classes, batch/queueable/schedulable jobs, or touches .cls/.trigger files. DO NOT TRIGGER when: LWC JavaScript (use sf-lwc), Flow XML (use sf-flow), SOQL-only queries (use sf-soql), or non-Salesforce code.
swift-development
IncludedComprehensive Swift development for building, testing, and deploying iOS/macOS applications. Use when Claude needs to: (1) Build Swift packages or Xcode projects from command line, (2) Run tests with XCTest or Swift Testing framework, (3) Manage iOS simulators with simctl, (4) Handle code signing, provisioning profiles, and app distribution, (5) Format or lint Swift code with SwiftFormat/SwiftLint, (6) Work with Swift Package Manager (SPM), (7) Implement Swift 6 concurrency patterns (async/await, actors, Sendable), (8) Create SwiftUI views with MVVM architecture, (9) Set up Core Data or SwiftData persistence, or any other Swift/iOS/macOS development tasks.