speckit-workflows.modify

Modify existing features with impact analysis and backward compatibility tracking.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/refactory-lang/refactory-template --skill speckit-workflows-modify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speckit-workflows.modify
Source: https://github.com/refactory-lang/refactory-template/tree/main/.claude/skills/speckit-workflows.modify
Command: npx skills add https://github.com/refactory-lang/refactory-template --skill speckit-workflows-modify

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the process of modifying existing features by providing impact analysis and ensuring backward compatibility, reducing the risk of introducing regressions.

Core Features & Use Cases

  • Feature Modification: Update existing features with detailed descriptions and impact tracking.
  • Impact Analysis: Automatically identifies affected files and contracts.
  • Backward Compatibility: Helps maintain stability by considering compatibility.
  • Use Case: A product manager needs to update a user authentication feature. This Skill can identify all related code, database schemas, and API contracts that will be affected by the change, and help document the modification process.

Quick Start

Use the speckit workflows modify skill to update feature 014 with the description "add avatar compression".

Frequently Asked Questions about speckit-workflows.modify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I modify an existing feature while checking backward compatibility?

Impact analysis for feature modification identifies affected files, database schemas, and API contracts before making changes. It operates within a .specify project structure to track backward compatibility and document the modification process automatically.

Do I need a .specify project structure to perform impact analysis on feature modifications?

Yes, a .specify project structure is required to execute impact analysis for feature modifications. The system utilizes bash scripts within this environment to analyze affected files and track backward compatibility during feature development.

How do I update a specific feature using a modification description?

You can update a specific feature by specifying its feature number directly or providing an interactive selection based on your modification description. This triggers an automated impact analysis to track all affected files and contracts.

What is the best way to analyze the impact of updating a user authentication feature?

The best way to analyze the impact of updating a user authentication feature is using automated impact analysis. It identifies all related code, database schemas, and API contracts affected by the change while ensuring backward compatibility.

Can I identify affected API contracts and database schemas before modifying a feature?

Yes, you can identify affected API contracts and database schemas before modifying a feature. The impact analysis mechanism automatically detects these dependencies to help document the modification process and maintain system stability.