What problem does it solve? After a feature is implemented and validated, teams need a controlled way to update the canonical specification so it reflects the system's new true state. This Skill is the only phase of the SDD harness permitted to write inside spec/, and it refuses to run unless validation has passed, preventing false claims from entering trusted documentation. ## Core Features & Use Cases - Guarded promotion: Refuses to run unless validation.md reports pass, spec-delta.md is still proposed, and all prior tasks are checked, naming exactly which precondition failed. - State-based spec writing: Applies the delta by writing the system's new current state rather than a changelog, reconciling sections instead of appending duplicates. - Cycle bookkeeping: Marks the delta promoted, checks off the final task, and appends a metrics row to cycles/index.md for tracking cycle size, scenarios, and validation attempts. - Use Case: After sdd-validate confirms an episodes timeline feature works, run this Skill to merge the proposed spec-delta into spec/, close the cycle folder, and log the cycle in the index. ## Quick Start Say "promove a spec" or "aplica o delta" after validation has passed to apply the proposed spec-delta into the canonical spec and close the cycle.
