Software Change Specification

Specify an accepted but ambiguous software change before implementation by recovering current and desired behavior, scope, invariants, affected surfaces, acceptance claims, and unresolved decisions. Use when implementers would otherwise invent consequential behavior. Do not use to review a fixed candidate; use specification-review. Keep small clear changes in scoped-change-implementation; route unresolved specialist decisions to their owners.

zhuochun Updated 1 repo stars

File contents

zhuochun/skills commit 05d941864a

Frequently asked questions

npx get-skill add zhuochun/software-change-specification