implement-change

Files (2)

• SKILL.md
• LICENSE.txt · references/

SKILL.md (first lines)

# Implement a change

1. Establish the behavior contract, affected callers, and state ownership before
   editing. Resolve consequential design uncertainty before committing to a shape.
2. Capture the relevant baseline. For refactoring, pin existing behavior with an
   executable characterization or equivalence check before moving structure.
3. Make the smallest coherent unit of change. Keep one owner for mutable state;
   isolate independent writers and serialize edits that share a target.
4. Update callers with changed interfaces. Remove obsolete internal paths when
   migration is complete; retain compatibility only for a concrete consumer need.
5. Verify each meaningful unit against its contract, then check the integrated
   result. Investigate repeated workarounds as a possible design error.
6. Inspect the final diff for unrelated edits, temporary scaffolding, and remaining
   obsolete paths. Explain any intentional behavior change separately from cleanup.

Done when the requested behavior works with evidence, existing contracts hold,
and remaining limitations are explicit. Preserve unrelated work; publication is
controlled by the enclosing task's scope.

Adapted from pstack; [license and attribution](references/LICENSE.txt).

From wcygan/agent-skills, MIT.

More from wcygan/agent-skills