Skill 5: SDD-Apply-Change
What SDD-Apply-Change Does
SDD-Apply-Change Applies one prepared change, a delta identified by its slug, to code that has already been generated. This is surgical editing of existing code, not regeneration. The specs are read-only; the run writes only inside the repository: the code, the ledger, and the implementation maps.
Run it once per change. Each run sees the previous run’s edits, which lets it notice a change arriving against code that an earlier one already moved.
Example prompts
Apply fix-01-orders-shipping to ./generated, specs at ./specs-sanitized
Implement the pending change fix-02-users-table in the generated repo
Bring ./generated up to date with fix-03-payment-retry from ./specs-sanitized
If you name the change loosely, you will be shown the candidates and asked to pick.
What You Get
- The change made in the code, with tests updated
openspec/changes-applied.mdupdated, so a later run knows this slug is done- Updated implementation maps
The run stops to ask whenever what it finds is not what it expected:
- the delta sits under
changes/spent/rather thanchanges/pending/ - the specs and repository do not look like they belong together
- the code does not match what the delta describes
- the change proves to be partly applied already
Each of these has more than one plausible cause, so the decision is yours, not the agent’s.