SpecSwarm Modify FAQs

Question 1

When should I use SpecSwarm Modify instead of other skills?

Accepted Answer

Use SpecSwarm Modify when you need to change, update, or extend a feature that is currently working but needs to behave differently. It is specifically designed for modifications rather than fixing bugs (use specswarm-fix) or building entirely new features (use specswarm-build).

Question 2

What is the confidence-based execution model?

Accepted Answer

The skill evaluates the clarity of your request. For clear instructions like 'Change auth to JWT', it auto-executes to save time. For ambiguous requests, it uses the AskUserQuestion tool to confirm intent, ensuring the AI never performs major modifications without proper alignment.

Question 3

What does the SpecSwarm Modify skill do?

Accepted Answer

This skill automates the workflow for modifying existing features. It performs an impact-analysis-first assessment to identify potential breaking changes, evaluates backward compatibility, and updates project specifications before implementing code changes.

Question 4

How does this skill improve my development workflow?

Accepted Answer

It reduces technical debt and deployment risks by catching breaking changes early. By generating migration plans and running regression tests automatically, it ensures that feature updates don't inadvertently disrupt existing system dependencies.

Question 5

Does SpecSwarm Modify handle the deployment of code?

Accepted Answer

No. The skill focuses on analysis, implementation, and validation. It stops once the modifications are complete and tested, allowing developers to manually review the changes before merging, shipping, or deploying to production.

SpecSwarm Modify

SpecSwarm Modify

概要

主な機能

ユースケース

概要

主な機能

ユースケース