speckit-simplify

Safely simplifying accepted code changes requires applying small refactoring edits within the approved write scope and rerunning validation checks. This constrained cleanup pass improves maintainability while preserving existing behavior and validation evidence.

Behavior-preservation validation in code refactoring is the process of rerunning relevant validation commands after edits to verify that simplifications do not change functionality. It records what changed, what stayed the same, and identifies any remaining risk.

You should run a code simplification pass on an accepted feature when it has already passed acceptance and you need a cleaner implementation. This occurs before the final quick acceptance step to improve maintainability without expanding the approved write scope.

No, you cannot expand the write scope during a post-acceptance cleanup pass. Simplifications must remain constrained inside the approved write scope to ensure behavior-preservation and avoid reopening the accepted feature scope.

To simplify spec-kit repositories after acceptance, review the accepted scope and validation evidence, apply small behavior-preserving edits, rerun validation commands, and log progress before handing off to quick acceptance. This constrained approach ensures safe cleanup.

A key limitation when refactoring accepted CoreRuntime code changes is that simplifications must stay within the approved write scope. Expanding scope or skipping validation reruns risks breaking behavior-preservation and invalidating existing acceptance evidence.